0ea8a7f3 kib May 3, 2021, 11:38 a.m. 
Fix what appears to have been a small copy/paste typo in ifconfig(8)'s
documentation (man page and header file).

Not that it matters anymore.

Reference: Table I-2 in IEEE Std 802.1Q-2014.

PR:	255557
Submitted by:	Jose Luis Duran <jlduran@gmail.com>
MFC after:	1 week
cgit
0ec20519 andrew May 3, 2021, 8:36 a.m. 
This was missed in 2420f6a

Reported by:	tuexen, imp
cgit
5c4fe2ac donner May 3, 2021, 10:27 a.m. 
Once the ipfw0 interface has been created, ifconfig(8) create will
throw a warning: ifconfig: create: bad value' when trying to create it
again.

PR:		241013
Submitted by:	Jose Luis Duran
Approved by:	kp
MFC after:	2 weeks
Differential Revision: https://reviews.freebsd.org/D30083
cgit
cff133b0 pho May 3, 2021, 7:08 a.m.
a7d46ad0 pho May 3, 2021, 7:05 a.m.
573bd33a pho May 3, 2021, 6:45 a.m.
8b3d0f64 tuexen May 3, 2021, 12:50 a.m. 
If the alternate address has to be removed, force the stack to
find a new one, if it is still needed.

MFC after:	3 days
cgit
a89481d3 tuexen May 3, 2021, 12:20 a.m. 
This fixes in particular a possible use after free bug reported
Anatoly Korniltsev and Taylor Brandstetter for the userland stack.

MFC after:	3 days
cgit
655c200c mav May 3, 2021, 12:07 a.m.
2760658b mav May 2, 2021, 11:45 p.m. 
When estimating working set size, measure only allocation batches, not free
batches.  Allocation and free patterns can be very different.  For example,
ZFS on vm_lowmem event can free to UMA few gigabytes of memory in one call,
but it does not mean it will request the same amount back that fast too, in
fact it won't.

Update working set size on every reclamation call, shrinking caches faster
under pressure.  Lack of this caused repeating vm_lowmem events squeezing
more and more memory out of real consumers only to make it stuck in UMA
caches.  I saw ZFS drop ARC size in half before previous algorithm after
periodic WSS update decided to reclaim UMA caches.

Introduce voluntary reclamation of UMA caches not used for a long time. For
each zdom track longterm minimal cache size watermark, freeing some unused
items every UMA_TIMEOUT after first 15 minutes without cache misses. Freed
memory can get better use by other consumers.  For example, ZFS won't grow
its ARC unless it see free memory, since it does not know it is not really
used.  And even if memory is not really needed, periodic free during
inactivity periods should reduce its fragmentation.

Reviewed by:	markj, jeff (previous version)
MFC after:	2 weeks
Sponsored by:	iXsystems, Inc.
Differential Revision:	https://reviews.freebsd.org/D29790
cgit
5f2e1835 tuexen May 2, 2021, 8:41 p.m. 
When processing INIT and INIT-ACK information, also during
COOKIE processing, delete the current association, when it
would end up in an inconsistent state.

MFC after:	3 days
cgit
4f592683 rmacklem May 2, 2021, 11:04 p.m. 
PR#255523 reported that a file copy for a file with a large hole
to EOF on ZFS ran slowly over NFSv4.2.
The problem was that vn_generic_copy_file_range() would
loop around reading the hole's data and then see it is all
0s. It was coded this way since UFS always allocates a data
block near the end of the file, such that a hole to EOF never exists.

This patch modifies vn_generic_copy_file_range() to check for a
ENXIO returned from VOP_IOCTL(..FIOSEEKDATA..) and handle that
case as a hole to EOF. asomers@ confirms that it works for his
ZFS test case.

PR:	255523
Tested by:	asomers
Reviewed by:	asomers
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D30076
cgit
bf7cc0f9 donner May 2, 2021, 7:28 p.m. 
ipfw -[tT] prints statistics of the last access. If the rule was never
used, the counter might be not exist.  This happens unconditionally on
inserting a new rule.  Avoid printing statistics in this case.

PR:	255491
Reported by:	Haisheng Zhouz
Reviewed by:	ae
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D30046
cgit
f6b6d216 delphij May 2, 2021, 4:30 p.m. 
MFC after:	 2 weeks
cgit
9769f6f8 delphij May 2, 2021, 4:27 p.m. 
MFC after:	2 weeks
cgit