| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
overflow in resolver described in FreeBSD-SA-02:28.resolv.
Binaries built and contributed by; motoyuki
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
represent their purpose and minimize namespace conflicts:
kse_fn_t -> kse_func_t
struct thread_mailbox -> struct kse_thr_mailbox
thread_interrupt() -> kse_thr_interrupt()
kse_yield() -> kse_release()
kse_new() -> kse_create()
Add missing declaration of kse_thr_interrupt() to <sys/kse.h>.
Regenerate the various generated syscall files. Minor style fixes.
Reviewed by: julian
|
| |
|
|
|
|
|
|
|
| |
automatically be enabled if the kernel is compiled with COMPAT_LINUX.
Submitted by: jhb
MFC after: 3 days
|
| |
|
|
|
|
| |
Submitted by: marius@alchemy.franken.de
|
|
|
|
|
|
|
| |
0 is never returned.
PR: 41781
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
fill_reject_code(). Please note ipfw/ipfw2.c is not affected.
PR: bin/42304
Submitted by: Andy@wantpackets.com
MFC after: 1 day
|
|
|
|
| |
Its Just Too Noisy.
|
|
|
|
| |
Its Just Too Noisy.
|
|
|
|
| |
Its Just Too Noisy.
|
|
|
|
| |
for it (via WANT_LINT). It's Just Too Noisy.
|
|
|
|
|
|
| |
PR: bin/41721
Reviewed by: tjr, silence on -audit
MFC after: 2 weeks
|
| |
|
|
|
|
| |
s/FALL THROUGH/FALLTHROUGH/ for lint(1).
|
|
|
|
|
| |
s/FALL THROUGH/FALLTHROUGH/ for lint(1).
s/Usage/usage/ for consistency.
|
|
|
|
|
|
|
|
| |
"Could you do me a favor and fix sys_bsd.c to get the howmany() macro
from <sys/param.h>, instead of <sys/types.h>? This will save me from
having to worry about the unsync'd bits before making the change."
Requested by: mike
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
aac driver dependent on the linux emulation module. This was
especially bad for the release engineers who tried to move the
aac driver from the kernel onto the drivers floppy. The linux
compat bits for this driver are now in their own driver, aac_linux.
It can be loaded as a module or compiled into the kernel. For
the latter case, the AAC_COMPAT_LINUX option is needed, along with
the COMPAT_LINUX option.
I've tested this in every configuration I can think of. This is an
MFC candidate for 4.7.
Idea from: rwatson
MFC after: 3 days
|
|
|
|
|
| |
with ports/Mk/bsd.ports.mk rev. 1.424. (It now prints the origin
after the package name.)
|
| |
|
|
|
|
| |
of pkg_version in periodic/weekly/400.status-pkg.
|
| |
|
|
|
|
|
|
| |
- Lock access to the buflists.
- Document broken locking.
- Use vrefcnt().
|
|
|
|
| |
- Use vrefcnt().
|
|
|
|
| |
- Convert interlock locks to use standard macros.
|
| |
|
| |
|
| |
|
|
|
|
| |
vnode interlock.
|
|
|
|
|
| |
- Use vrefcnt() where appropriate.
- Add some locking asserts.
|
|
|
|
| |
- Use vrefcnt() where appropriate.
|
| |
|
|
|
|
|
|
|
| |
unlocked accesses to v_usecount.
- Lock access to the buf lists in the various sync routines. interlock
locking could be avoided almost entirely in leaf filesystems if the
fsync function had a generic helper.
|
|
|
|
| |
- Fixup interlock locking in spec_close()
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Enable vfs_badlock_mutex by default.
- Assert that the vp is locked in VOP_UNLOCK.
- Use standard interlock macros in remaining code.
- Correct a race in getnewvnode().
- Lock access to v_numoutput with interlock.
- Lock access to buf lists and splay tree with interlock.
- Add VOP and VI asserts.
- Lock b_vnbufs with the vnode interlock.
- Add vrefcnt() for callers who want to retreive the vnode ref without
holding a lock. Add a comment that describes when this is safe.
- Add vholdl() and vdropl() so that callers who already own the interlock
can avoid race conditions and unnecessary unlocking.
- Move the VOP_GETATTR() in vflush() into the WRITECLOSE conditional case.
- Hold the interlock before droping the mntlist_mtx in vflush() to avoid
a race.
- Fix locking in vfs_msync().
|
| |
|
|
|
|
| |
- Lock access to numoutput.
|
|
|
|
| |
- Lock calls to gbincore.
|
|
|
|
| |
headaches for common but deprecated uses of standard utilities.
|
|
|
|
| |
- Protect mountedhere with the vn lock.
|
| |
|
|
|
|
| |
- Order fields by what lock is required to access them.
|
| |
|
| |
|
|
|
|
| |
- Lock access to v_iflags.
|
| |
|
| |
|
|
|
|
| |
that instruction emulation is possible in kernel mode.
|