| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
when it is not really used instead of unconditionalizing all of it.
|
| |
|
|
|
|
| |
as NetBSD's definitions.
|
| |
|
|
|
|
|
|
| |
It's more important to keep this file easily syncable across the
BSDs, and NetBSD have stated a preference for not adding them to
theirs.
|
|
|
|
|
|
|
|
|
| |
kern_prot.c. This has apparently been sitting in my local tree for
ages, and has been generating a warning during the building of
kern_prot.o.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| |
|
|
|
|
| |
uninitialized variable in the !CY_PCI_FASTINTR case (*blush*).
|
|
|
|
|
|
|
|
|
|
|
| |
call VOP_INACTIVE before placing the vnode back on the free list.
Otherwise there is a race condition on SMP machines between
getnewvnode() locking the vnode to reclaim it and vrele()
locking the vnode to inactivate it. This window of vulnerability
becomes exaggerated in the presence of filesystems that have
been suspended as the inactive routine may need to temporarily
release the lock on the vnode to avoid deadlock with the syncer
process.
|
|
|
|
|
|
| |
been unlinked (e.g., with a zero link count). We have to expunge
all trace of these files from the snapshot so that they are neither
reclaimed prematurely by fsck nor saved unnecessarily by dump.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
threads race for a file slot.
dup2(2) incorrectly assumes that if it needs to grow the ofiles
array that it will get what it wants. This assertion was valid
before we allowed shared filedescriptor tables but is now incorrect.
The assertion can trigger superfolous panics if the thread doing a
dup2 looses a race with another thread while possibly blocked in
the MALLOC call in fdalloc. Another thread may grab the slot we
are requesting which makes fdalloc return something other than what
we asked for, this will triggering the bogus assertion.
MFC after: 2 weeks
Reviewed by: phk
|
|
|
|
|
|
| |
by unlocking the filedesc before calling FREE().
Submitted by: bde
|
|
|
|
| |
Noticed by: Michael Nottebrock <michaelnottebrock@gmx.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
signal trampoline for old signals. The arches that support old signals
currently abuse sigreturn(2) instead. This mainly complicates things
and slightly breaks the the new sigreturn(2).
COMPAT is too limited to support the correct configuration of osigreturn,
and this commit doesn't attempt to fix it; it just moves the bogusness:
osigreturn() must now be provided unconditionally even on arches that
don't really need it; previously it had to be provided under the bogus
condition defined(COMPAT_43).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
some arches and the syscall table is machine-independent. It was
(bogusly) conditional on COMPAT_43, so this usually makes no difference.
ia64: in addition:
- replace the bogus cloned comment before osigreturn() by a correct one.
osigreturn() is just a stub fo ia64's.
- fix the formatting of cloned comment before sigreturn().
- fix the return code. use nosys() instead of returning ENOSYS to get
the same semantics as if the syscall is not in the syscall table.
Generating SIGSYS is actually correct here.
- fix style bugs.
powerpc: copy the cleaned up ia64 stub. This mainly fixes a bogus comment.
sparc64: copy the cleaned up the ia64 stub, since there was no stub before.
|
| |
|
|
|
|
|
|
|
|
| |
'struct ng_ksocket_sockopt') like to peek into the ng_mesg header for
information. Make sure when generating default values that we provide
a valid header to peek into.
MFC after: 1 week
|
|
|
|
|
| |
* Remove 'register'. (some functions had 7+ register functions...)
* Fix SCM ID's.
|
|
|
|
|
|
| |
cache lockups for over a year now.
MFC after: 0 days
|
|
|
|
| |
Submitted by: Toni Andjelkovic <toni@soth.at>
|
|
|
|
|
|
|
|
|
| |
for SMP in the plain profiling case. It seems to work too.
This error was not detected by LINT because LINT only compiles the
GUPROF profiling case, which is is a superset of the plain profiling
case for !SMP but which is so broken for SMP that the buggy code is
not compiled.
|
|
|
|
|
|
|
|
|
| |
- Vendor&Device IDs for USB product,
- quirk for SCSI CAM.
PR: 34481
Submitted by: Olexander Kunytsa <kunia@x-telecom.net>
MFC in: 3 days
|
|
|
|
|
| |
in one object for one resource. Array of values in a object means
possible values for the object.
|
| |
|
| |
|
|
|
|
| |
respectively.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR:30665
Submitted by:TOMITA Yoshinori <yoshint@flab.fujitsu.co.jp>
|
|
|
|
| |
not tested under LINT by: msmith
|
|
|
|
| |
Noticed by: Vincent Poy <vince@oahu.WURLDLINK.NET>
|
|
|
|
|
|
|
|
| |
SIOCSIFMAC, which are for the Mandatory Access Control
implementation. This will prevent collisions on the p4 development
branch.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
|
| |
sort declaration.
give paramters names.
remove bogus check for negative fd (u_int) cast does this for us.
Pointed out by: bde
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
|
|
|
| |
the packet transfer routines, since rev.1.468 of machdep.c does this
better. I'm surprised that disabling interrupts helped much. Disabling
them in the packet receive routine is too late.
Fixed some minor style bugs in rev.1.14.
|
|
|
|
|
| |
region in Debugger(), since rev.1.468 of machdep.c does this better.
Other cosmetic backouts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to fetch the magic word instead of useracc() plus a direct access.
This is more efficient as well as simpler and less incorrect:
- it was inefficent because useracc() takes much longer than just
accessing the data using a correct access method, at least on i386's.
- it was incorrect because direct access is incorrect unless the address
has been mapped. This and nearby direct accesses are mostly handled
better for other arches because they have to be (direct accesses don't
work).
- using magic in sigreturn is still fundamentally broken because false
matches are possible. On i386's, a false match occurs when %eip in a
new signal context happens to equal the magic value. This is not
handled better for other arches.
|
|
|
|
|
|
|
| |
standard one of 1.8432MHz. This will be used by the puc (PCI
"universal" communication card) device driver.
Reviewed by: bde
|
|
|
|
| |
commit broke the world in libc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
npx is no more mandatory than sc. Its mandatoryness went away in
rev.1.226 of i386/machdep.c 9 months before it was made mandatory in
rev.1.24 of config/mkmakefile.c.
This change is mainly to test building of minimal kernel configurations.
npx should really be even more standard than clk. It was optional mainly
so that the usual device driver configuration info could be specified in
the usual way in config files, but this hasn't been necessary for a few
years.
|
|
|
|
|
|
|
|
| |
is not configured. Including <isa/isavar.h> when it is not used is
harmful as well as bogus, since it includes "isa_if.h" which is not
generated when isa is not configured.
This was fixed in 1999 but was broken by unconditionalizing PNPBIOS.
|
|
|
|
|
|
| |
its only effect is to break the optionality of the isa option.
Sorted includes.
|
| |
|
|
|
|
| |
and \F. Awk just started warning about these.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
other threads as well as speed up the interfaces.
To fix the race and accomplish the speedup, remove selholddrop and
pollholddrop. The entire concept is somewhat bogus because holding
the individual struct file pointers offers us no guarantees that
another thread context won't close it on us thereby removing our
access to our own reference.
Selholddrop and pollholddrop also would do multiple locks and unlocks
of mutexes _per-file_ in the fd arrays to be scanned, this needed to
be sped up.
Instead of using selholddrop and pollholddrop, simply hold the
filedesc lock over the selscan and pollscan functions. This should
protect us against close(2)'s on the files as reduce the multiple
lock/unlock pairs per fd into a single lock over the filedesc.
|
|
|
|
|
|
|
| |
negative, the 'pointer' referred to by the manpage is actually the
struct file's f_offset field.
Pointed out by: bde
|