| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
subr_bus.c doesn't need to peek inside struct resource.
OK from: imp
|
|
|
|
|
|
| |
Replace a KASSERT of LINUX_IFNAMSIZ == IFNAMSIZ with a preprocessor
check and #error message. This will prevent nasty suprises if users
change IFNAMSIZ without updating the linux code appropriatly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LD_LIBMAP_DISABLE, LD_LIBRARY_PATH) are used, then make sure the
libraries being loaded aren't on a noexec-mounted filesystem.
This is a compromise position: I'm assuming that nobody will be silly
enough to set the noexec mount flag on part of the default library
path, in order to avoid adding extra overhead into the common case
(where those environment variables aren't used).
Discussed with: csjp, secteam
MFC after: 1 week
|
|
|
|
|
|
| |
userret().
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
| |
lockmgr locks that this thread owns. This is complicated due to
LK_KERNPROC and because lockmgr tolerates unlocking an unlocked lock.
Sponsored by: Isilon Systes, Inc.
|
|
|
|
|
|
|
|
| |
these filesystems will support shared locks until they are explicitly
modified to do so. Careful review must be done to ensure that this
is safe for each individual filesystem.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
| |
these filesystems will support shared locks until they are explicitly
modified to do so. Careful review must be done to ensure that this
is safe for each individual filesystem.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
| |
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
| |
- Pass the ufs_root() flags argument to VFS_VGET() to allow callers to
specify shared locks.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
| |
now, all calls to VFS_ROOT() should still acquire exclusive locks.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
| |
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
| |
lookup to do shared locks on the root. Filesystems are free to ignore
flags and instead acquire an exclusive lock if they do not support
shared locks.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
| |
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
|
|
|
| |
before it can call VOP_INACTIVE(). This must use the EXCLUPGRADE path
because we may violate some lock order with another locked vnode if
we drop and reacquire the lock. If EXCLUPGRADE fails, we mark the
vnode with VI_OWEINACT. This case should be very rare.
- Clear VI_OWEINACT in vinactive() and vbusy().
- If VI_OWEINACT is set in vgone() do the VOP_INACTIVE call here as well.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
| |
- Always pass LOCKSHARED and rely on namei() to ignore it when
LOOKUP_SHARED is not set.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
| |
LOCKSHARED flag is simply ignored in namei() if LOOKUP_SHARED is not
enabled.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
| |
necessary since we disable the shared locks in vfs_cache, but it is
prefered that the option not leak out into filesystems when it is
disabled.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
| |
config option have now been fixed. All filesystems are properly locked
and checked via DEBUG_VFS_LOCKS. Remove the workaround code.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
| |
PR: docs/78322
Submitted by: Joel Dahl <joel@automatvapen.se>
Approved by: trhodes (mentor)
|
|
|
|
| |
- Default returns an error.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
non-maskable).
- The NFS client needs to guard against spurious wakeups
while waiting for the response. ltrace causes the process
under question to wakeup (possibly from ptrace()), which
causes NFS to wakeup from tsleep without the response being
delivered.
Submitted by: Mohan Srinivasan
|
|
|
|
|
|
|
| |
pci_set_powerstate_method function...
Reviewed by: imp
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
we weren't using the pci module, we weren't restoring the pci state...
Submitted by: imp
MFC after: 5 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
disables tag queuing temporarily in order to allow controllers a window
to safely perform transfer negotiation with non-compliant devices. Before
this change, CAM would restore the queue depth to the controller specified
maximum or device quirk level rather than any depth determined by reactions
to QUEUE FULL/BUSY events or an explicit user setting.
During device probe, initialize the flags field for XPT_SCAN_BUS.
The uninitialized value often confused CAM into not bothering to
issue an AC_FOUND_DEVICE async event for new devices. The reason
this bug wasn't reported earlier is that CAM manually announces
devices after the initial system bus scans.
MFC: 3 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Update the description of the cdrom.1 target and add notes for cdrom.2
and cdrom.3.
- Document CD_PACKAGES_TREE (CD_EXTRA_BITS wasn't documented before).
- Document CVSARGS.
- Remove DISC[12]_{LABEL,NAME}.
- Remove NOPORTREADMES.
- Remove references to drivers.conf files and man page.
- Update version number for a CURRENT snapshot to 6.0.
|
|
|
|
| |
supporting scripts were removed as part of the splitfs floppy rework.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- When a separate livefs ISO is used, change the name of the tree directory
to be R/cdrom/livefs and change the name of the iso to livefs.iso rather
than using disc2. Instead, disc2 is now always going to be the packages
disc regardless of the presence of a separate livefs which makes things
simpler.
- Build a very simple disc2 tree under R/cdrom that just includes the
cdrom.inf file that the packages need. Also, build a disc2.iso image
in the iso.1 target. Disc 2's volume label is "FreeBSD_Packages".
- Retire CD_EXTRA_BITS and replace it with CD_PACKAGE_TREE. CD_EXTRA_BITS
was specific to disc1, but CD_PACKAGE_TREE instead should point to a
directory that has disc1 and disc2 subdirectories that contain the extra
bits for each image.
- Rename the bootonly volume label to "FreeBSD_bootonly" and just hardcode
the disc1 and livefs volume names and iso suffixes.
|
|
|
|
|
|
| |
A Path is now a TAILQ of PathElements each of which just points to
a reference counted directory. Rename all functions dealing with Paths
from the Dir_ prefix to a Path_ prefix.
|
|
|
|
|
| |
is handled.
- Xref flowctl.8
|
| |
|
|
|
|
| |
of Cisco's "show ip cache verbose flow" command.
|
|
|
|
|
|
|
|
| |
o Correct a comment about random port allocation threshold
implementation.
Reviewed by: silby, ru
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
svr4_do_getmsg(). In principle this bug could disclose data from
kernel memory, but in practice, the SVR4 emulation layer is probably
not functional enough to cause the relevant code path to be executed.
In any case, the emulator has been disconnected from the build since
5.0-RELEASE.
Found by: Coverity Prevent analysis tool
|
|
|
|
|
|
|
|
|
| |
to kmem_alloc(). Failure to do this made it possible for user
processes to cause a hard lock on i386 kernels. I believe this only
affects 6-CURRENT on or after 2005-01-26.
Found by: Coverity Prevent analysis tool
Security: Local DOS
|
|
|
|
|
|
|
|
|
|
|
| |
with the IP_HDRINCL option set. Without this change, a Linux process
with access to a raw socket could cause a kernel panic. Raw sockets
must be created by root, and are generally not consigned to untrusted
applications; hence, the security implications of this bug are
minimal. I believe this only affects 6-CURRENT on or after 2005-01-30.
Found by: Coverity Prevent analysis tool
Security: Local DOS
|
|
|
|
|
|
|
|
|
|
|
| |
validation error in procfs/linprocfs that can be exploited by local
users to cause a kernel panic. All versions of FreeBSD with the patch
referenced in SA-04:17.procfs have this bug, but versions without that
patch have a more serious bug instead. This problem only affects
systems on which procfs or linprocfs is mounted.
Found by: Coverity Prevent analysis tool
Security: Local DOS
|
|
|
|
|
|
|
|
|
|
|
|
| |
variable, because it might be not obvious how to configure carp(4)
devices in rc.conf.
2. Remove the sentence about the not implemented "carpdev" option (this
was not imported from OpenBSD according to our source code) to avoid
confusion.
Reviewed by: glebius@
MFC after: 3 days
|
|
|
|
|
|
|
| |
that it really wasn't intended as a security feature.
Wording mostly by: simon
Discussed with: secteam
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
there are still a couple of places under src/release such like fixit.profile
assumed that system binary can be retrivied from /stand(ex: boot with the
live CD and run "disklabel -e" in the fixit CD shell).
Since /stand is still functional in fixit floppy, and there are more than
one places in src/release needs to be updated(document for example) if we
want to make use of something like /mnt2/rescue/vi. This commit try to
deal with aforementioned inconsistency with minimal effort by simply
create a symbolic link to /rescue.
Reviewed by: jhb, sam (mentor)
|
|
|
|
|
| |
Reported by: stefanf
MFC after: 3 days
|
|
|
|
| |
this before setting a new resource.
|