| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
flag from a mount flag to FS-specific flag.
- Simplify usage. Instead of 'mksnap_ffs /mnt/foo /mnt/foo/snap' allow to
give only one argument: 'mksnap_ffs /mnt/foo/snap'. Old usage is also
accepted for now.
- Add an example of how to mount a snapshot.
|
|
|
|
| |
to UPDATING.
|
| |
|
|
|
|
|
| |
than using the kernel object. This allows the elimination of page queues
locking from vm_hold_free_pages().
|
|
|
|
|
|
|
|
|
|
|
|
| |
ipfilter tables via http by the user-level ippool utility. Previously
the 1024-byte buffer used to store a http request coudld easily overflow
if the length of the hostname part of the url passes exceeded 496 bytes. [1]
- Use snprintf to prevent possieble buffer overflows in future. [2]
- Do not try to close the descriptor twice on failure. [2]
Reported by: Maksymilian Arciemowicz <cxib@securityreason.com> [1]
Obtained from: NetBSD CVS [2]
MFC after: 2 weeks
|
|
|
|
| |
Spotted by: HPS
|
|
|
|
|
|
| |
Make room for additional filesystem flags now, to avoid breaking ABI later.
Reviewed by: kib@
|
| |
|
|
|
|
| |
inline in rmlocks.
|
|
|
|
|
|
|
| |
in tight spin loops, not in these edge cases where we restart a much
larger loop only a few times.
Reviewed by: attilio
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "wall clock" in the current code is actually the hypervisor start time.
The time of day is the "start time" plus the hypervisor "uptime".
Large enough bumps in the dom0 clock lead to a hypervisor "bump" which is
implemented as a bump in the start time, not the uptime. The clock.c routines
were reading in the hypervisor start time and then using this as the TOD.
This meant that any hypervisor time bump would cause the FreeBSD DomU to
set its TOD to the hypervisor start time, rather than the actual TOD.
This fix is a bit hacky and some reshuffling should be done later on
to clarify what is going on. I've left the wall clock code alone.
(The code which updates shadow_tv and shadow_tv_version.)
A new routine adds the uptime to the shadow_tv, which is then used to
update the TOD.
I've included some debugging so it is obvious when the clock is nudged.
PR: 135008
|
|
|
|
| |
sharable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add rm_init_flags() and accept extended options only for that variation.
- Add a flags space specifically for rm_init_flags(), rather than borrowing
the lock_init() flag space.
- Define flag RM_RECURSE to use instead of LO_RECURSABLE.
- Define flag RM_NOWITNESS to allow an rmlock to be exempt from WITNESS
checking; this wasn't possible previously as rm_init() always passed
LO_WITNESS when initializing an rmlock's struct lock.
- Add RM_SYSINIT_FLAGS().
- Rename embedded mutex in rmlocks to make it more obvious what it is.
- Update consumers.
- Update man page.
|
|
|
|
|
| |
PR: usb/135009
Submitted by: Bill Squire <billsf at 2600.COM>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the last component is a symlink to something that isn't a directory.
We introduce a new namei flag, TRAILINGSLASH, which is set by lookup()
if the last component is followed by a slash. The trailing slash is
then stripped, as before. If the final component is a symlink,
lookup() will return to namei(), which will expand the symlink and
call lookup() with the new path. When all symlinks have been
resolved, lookup() checks if the TRAILINGSLASH flag is set, and if it
is, and the vnode it ended up with is not a directory, it returns
ENOTDIR.
PR: kern/21768
Submitted by: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
Remove unused rm_initialized() macro.
|
| |
|
|
|
|
| |
PR: kern/129477
|
|
|
|
| |
PR: kern/129477
|
|
|
|
|
|
| |
PR: 129110
Submitted by: Mike Voorhis <mvoorhis@cs.wpi.edu>
MFC after: 3 weeks
|
|
|
|
|
|
| |
does not follow sysexits(3), and returns 1 for all error cases.
PR: docs/126451
|
|
|
|
|
|
|
|
|
|
| |
I don't want people to override the mutex when allocating a TTY. It has
to be there, to keep drivers like syscons happy. So I'm creating a
tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex()
should eventually be removed.
The advantage of this approach, is that we can just remove a function,
without breaking the regular API in the future.
|
|
|
|
|
|
| |
PR: kern/91293
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
|
|
|
|
|
|
|
|
| |
hostid of the machine rather than always getting "0".
PR: kern/91293
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
|
|
|
|
|
|
| |
PR: kern/91293
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
|
|
|
|
|
|
| |
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
PR: kern/91293
|
|
|
|
|
|
|
|
| |
everywhere.
PR: kern/91293
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
|
|
|
|
|
|
| |
Submitted by: "Pedro f. Giffuni" <giffunip asme org>
Obtained from: NetBSD
PR: kern/91293
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce for this operation the reverse NO_ADAPTIVE_SX option.
The flag SX_ADAPTIVESPIN to be passed to sx_init_flags(9) gets suppressed
and the new flag, offering the reversed logic, SX_NOADAPTIVE is added.
Additively implements adaptive spininning for sx held in shared mode.
The spinning limit can be handled through sysctls in order to be tuned
while the code doesn't reach the release, after which time they should
be dropped probabilly.
This change has made been necessary by recent benchmarks where it does
improve concurrency of workloads in presence of high contention
(ie. ZFS).
KPI breakage is documented by __FreeBSD_version bumping, manpage and
UPDATING updates.
Requested by: jeff, kmacy
Reviewed by: jeff
Tested by: pho
|
| |
|
|
|
|
| |
Approved by: gnn
|
| |
|
|
|
|
|
|
|
| |
confusion, since it does not refer to IPv4 nor NFSv4, but to
running the experimental server instead of the regular one.
Approved by: kib (mentor)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
includes support for NFSv4. The subsystem can optionally be linked
into the kernel using the two options:
NFSCL - the client
NFSD - the server
It is also built as three modules:
nfscl - the client
nfsd - the server
nfscommon - functions shared by the client and server
Approved by: kib (mentor)
|
|
|
|
| |
stricter.
|
| |
|
|
|
|
| |
expansion for this file.
|
|
|
|
|
| |
Suggested by: Ben Kaduk
Approved by: dfr (mentor)
|
|
|
|
|
|
|
| |
it's a little nicer).
Suggested by: jilles
Approved by: dfr (mentor)
|
|
|
|
|
| |
Suggested by: jhb
Approved by: dfr (mentor)
|
|
|
|
|
| |
Submitted by: kib
MFC after: 1 week
|
|
|
|
|
|
|
| |
uses the generic struct dirent, which happens to look identical to UFS's
struct direct. If BSD ever changes dirent then this will be a problem.
Submitted by: matthew dot fleming at isilon dot com
|
|
|
|
|
|
| |
- add FreeBSD implementation of xdrmem_control needed by zfs
- have zfs define xdr_ops using FreeBSD's definition
- remove solaris xdr files from zfs compile
|
|
|
|
|
|
|
|
|
|
| |
differently. The output now shows the ruleset and shortens to
slightly different text (using $daily_status_mail_rejects_shorten),
but it should be more descriptive.
PR: 35018
Inspired by: Mikhail Teterin - mi at aldan dot algebra dot com
MFC after: 3 weeks
|
|
|
|
|
|
| |
when it invalidates the page.
Suggested by: tegge
|
|
|
|
|
| |
Reviewed by: rwatson@
MFC after: 2 weeks
|