| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
race prone. Some just gather statistics, but some are later used in
different calculations.
A real problem was the race provoked underflow of the states_cur counter
on a rule. Once it goes below zero, it wraps to UINT32_MAX. Later this
value is used in pf_state_expires() and any state created by this rule
is immediately expired.
Thus, make fields states_cur, states_tot and src_nodes of struct
pf_rule be counter(9)s.
Thanks to Dennis for providing me shell access to problematic box and
his help with reproducing, debugging and investigating the problem.
Thanks to: Dennis Yusupoff <dyr smartspb.net>
Also reported by: dumbbell, pgj, Rambler
Sponsored by: Nginx, Inc.
|
|
|
|
| |
Sponsored by: Nginx, Inc.
|
|
|
|
|
|
| |
instead of spinning.
Reported by: Mikhail <mp@lenta.ru>
|
|
|
|
|
|
|
|
|
|
|
| |
fsck, the latter does not accept the referred to "-b" flag.
This change was accidently committed directly to 9-STABLE in
r237505.
PR: 82720
Submitted by: David D.W. Downey
MFC after: 1 week
|
|
|
|
|
|
|
| |
The tracking generated warnings when the line number of an existing tty in
/etc/ttys changed, which would corrupt utmp (as it was indexed by the line
number). With utmpx, the line number no longer matters, so the tracking is
no longer needed.
|
|
|
|
|
|
|
| |
PR: 185382 (based on)
Submitted by: Loganaden Velvindron
Reviewed by: pjd
MFC after: 1 week
|
|
|
|
|
|
| |
holder to convert them to 2 clause BSD licenses.
MFC after: 1 week
|
|
|
|
|
| |
Approved by: Stefan Bethke (original author, by private mail) (1)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
network packets that we parse and not against local users trying to gain root
access through ping's set-uid bit - this is handled by dropping privileges very
early in ping.
Submitted by: Mikhail <mp@lenta.ru>
|
|
|
|
|
|
|
|
| |
nmount(). This has been broken since r247856.
PR: bin/186193
Submitted by: Arnot Belohlavek
MFC after: 1 week
|
|
|
|
|
|
|
| |
This change permits non-root users to determine if dhclient is running
('service dhclient status wlan0').
Discussed with: mjg, cperciva
|
|
|
|
| |
Pointy hat: brueffer
|
|
|
|
|
|
| |
Fixes a typo in the process.
MFC after: 1 week
|
|
|
|
|
|
| |
PR: bin/180014
Submitted by: Olivier Cochard-Labbé <olivier@cochard.me>
MFC after: 1 week
|
|
|
|
| |
Reported by: trasz
|
|
|
|
| |
Reported by: dumbbell
|
|
|
|
|
|
|
|
| |
did fail
instead of printing the cryptic "Exec format error"
MFC after: 1 week
|
|
|
|
|
|
|
| |
Fix several small errors introduced by r260524.
Suggested by: glebius
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
It was equal before r259397, but for good or bad, not any more for LUNs.
This change fixes at least CAM debugging.
|
|
|
|
|
|
| |
give a hint to use 'gpart create' before trying to add a partition.
Approved by: pjd
|
| |
|
|
|
|
|
|
| |
already loaded or compiled withing the kernel
MFC after: 1 week
|
|
|
|
|
|
|
| |
the same address family as destination.
Found by: jmg
MFC after: 2 weeks
|
|
|
|
|
|
| |
calling process' umask.
Submitted by: Mikhail <mp@lenta.ru>
|
|
|
|
|
|
|
|
| |
GB to improve granularity of the reporting - especially for namespaces
that are on the order of 1 or 2 GB.
Submitted by: Tony Beltran <anthony.beltran@emc.com>
MFC after: 3 days
|
|
|
|
|
|
|
| |
power of 2.
Noticed by: rwatson
MFC after: 3 days
|
|
|
|
|
|
| |
the return value. Fixes powerpc tinderbox.
MFC after: 2 days
|
|
|
|
|
|
| |
Submitted by: peter
Obtained from: Netflix
MFC after: 3 Days
|
|
|
|
|
|
| |
Reviewed by: max
Obtained from: Netflix
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
errors have been detected in a particular run.
Clean up the global state variables so that a restart can happen correctly.
Separate the global variables in fsck_ffs and fsdb to their own file. This
fixes header sharing with fscd.
Correctly initialize, static-ize, and remove global variables as needed in
dir.c. This fixes a problem with lost+found directories that was causing
a segfault.
Correctly initialize, static-ize, and remove global variables as needed in
suj.c.
Initialize the suj globals before allocating the disk object, not after.
Also ensure that 'preen' mode doesn't conflict with 'restart' mode
Submitted by: scottl, max
Reviewed by: max, mckusick (earlier version)
Obtained from: Netflix
MFC after: 3 days
|
|
|
|
|
|
|
| |
buses and their parent sims, useful for creating a sim->bus->device map.
Obtained from: Netflix
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the problem, when gmirror starts again just after stop.
The problem occurs when gmirror's component has geom label with equal size.
E.g. gpt and gptid have the same size as partition, diskid has the same
size as entire disk. When gmirror's geom has been destroyed, glabel
creates its providers and this initiate retaste.
Now "gmirror destroy" command is available. It destroys geom and also
erases gmirror's metadata.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
INET6 socket when needed to allow pfctl to work on noinet and noinet6
kernels (and try to provide a fallback using AF_LINK as best effort).
Adjust the Makefile to also respect relevant src.conf(5) options
for compile time decisions on INET and INET6 support.
Reviewed by: glebius (no objections)
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/185057
Submitted by: Yuri (yuri@rawbw.com)
Approved by: gjb (mentor)
|
|
|
|
|
|
| |
PR: bin/184950
Tested by: Radim Kolar
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
re-links dynamic states to default rule instead of
flushing on rule deletion.
This can be useful while performing ruleset reload
(think about `atomic` reload via changing sets).
Currently it is turned off by default.
MFC after: 2 weeks
Sponsored by: Yandex LLC
|
|
|
|
|
| |
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
| |
Change casperd's zygote process title.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Promoting the SIGINFO handler's log message from LOG_INFO to
LOG_NOTICE, and promoting the "Processing event ..." message from
LOG_DEBUG to LOG_INFO. Setting the logfile to LOG_NOTICE with this
change will have the same result as setting it to LOG_INFO without
this change. Setting it to LOG_INFO with this change will include
the useful "Processing event ..." messages that were previously at
LOG_DEBUG, without including useless messages like "Pushing table".
The intent of this change is that one can log "Processing event ..."
without logging "Pushing table" and related messages that are sent
for every event. The number of lines actually logged is reduced by
about 75% by making this change and setting syslog to LOG_INFO vs
setting syslog to LOG_DEBUG.
etc/syslog.conf
Changing the recommended loglevel to notice instead of info.
Sponsored by: Spectra Logic Corp
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Increase the size of devd's client socket's send buffer from the
default (8k) to 128k. This prevents clients from getting
POLLHUPped during event storms. For example, during zpool creation,
the kernel emits a resource.fs.zfs.statechange event for every vdev
in the pool. A 128k buffer is large enough to hold the statechange
events for a pool with nearly 800 drives.
Reviewed by: ian, imp
Approved by: ken (mentor)
Sponsored by: Spectra Logic Corp
MFC after: 4 weeks
|
| |
|
|
|
|
|
|
|
|
|
| |
is actually sent by the remote node).
Otherwise it generated confusing "Negotiated protocol version 1" debug
messages when processing the second connection.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
lock to decrease spurious wakeups.
Submitted by: davidxu
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
request back from the receive queue -- it might already be processed
by remote_recv_thread, which lead to crashes like below:
(primary) Unable to receive reply header: Connection reset by peer.
(primary) Unable to send request (Connection reset by peer):
WRITE(954662912, 131072).
(primary) Disconnected from kopusha:7772.
(primary) Increasing localcnt to 1.
(primary) Assertion failed: (old > 0), function refcnt_release,
file refcnt.h, line 62.
Taking the request back was not necessary (it would properly be
processed by the remote_recv_thread) and only complicated things.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|