1. 24 Sep, 2021 21 commits
  2. 23 Sep, 2021 19 commits
    • Warner Losh's avatar
      nvme: Use shared timeout rather than timeout per transaction · 502dc84a
      Warner Losh authored
      Keep track of the approximate time commands are 'due' and the next
      deadline for a command. twice a second, wake up to see if any commands
      have entered timeout. If so, quiessce and then enter a recovery mode
      half the timeout further in the future to allow the ISR to
      complete. Once we exit recovery mode, we go back to operations as
      normal.
      
      Sponsored by:		Netflix
      Differential Revision:	https://reviews.freebsd.org/D28583
      502dc84a
    • Kristof Provost's avatar
      pf: fix pagefault in pf_getstatus() · cb130596
      Kristof Provost authored
      We can't copyout() while holding a lock, in case it triggers a page
      fault.
      Release the lock before copyout, which is safe because we've already
      copied all the data into the nvlist.
      
      PR:		258601
      Reviewed by:	mjg
      MFC after:	1 week
      Sponsored by:	Modirum MDPay
      Differential Revision:	https://reviews.freebsd.org/D32076
      cb130596
    • Wenzhuo Lu's avatar
      e1000: fix K1 configuration · d5ad2f2a
      Wenzhuo Lu authored
      
      
      This patch is for the following updates to the K1 configurations:
      Tx idle period for entering K1 should be 128 ns.
      Minimum Tx idle period in K1 should be 256 ns.
      Signed-off-by: default avatarWenzhuo Lu <wenzhuo.lu@intel.com>
      
      PR:		258153
      Reviewed by:	erj
      Tested by:	iron.udjin@gmail.com
      Approved by:	imp
      Obtained from:	DPDK (6f934fa24dfd437c90ead96bc7598ee77a117ede)
      MFC after:	1 week
      d5ad2f2a
    • Kyle Evans's avatar
      man: reset OPTIND before parsing args · f555b39e
      Kyle Evans authored
      From jilles: POSIX requires that a script set `OPTIND=1` before using
      different sets of parameters with `getopts`, or the results will be
      unspecified.
      
      The specific problem observed here is that we would execute `man -f` or
      `man -k` without cleaning up state from man_parse_args()' `getopts`
      loop.  FreeBSD's /bin/sh seems to reset OPTIND to 1 after we hit the
      second getopts loop, rendering the following shift harmless; other
      /bin/sh implementations will leave it at what we came into the loop at
      (e.g., bash as /bin/sh), shifting off any keywords that we had.
      
      Input from:	jilles
      Reviewed by:	allanjude, bapt, imp
      Sponsored by:	Klara, Inc.
      Differential Revision:	https://reviews.freebsd.org/D32063
      f555b39e
    • Alexander Motin's avatar
      x86: Add NUMA nodes into CPU topology. · ef50d5fb
      Alexander Motin authored
      Depending on hardware, NUMA nodes may match last level caches, or
      they may be above them (AMD Zen 2/3) or below (Intel Xeon w/ SNC).
      This information is provided by ACPI instead of CPUID, and it is
      provided for each CPU individually instead of mask widths, but
      this code should be able to properly handle all the above cases.
      
      This change should immediately allow idle stealing in sched_ule(4)
      to prefer load from NUMA-local CPUs to remote ones when the node
      does not match LLC.  Later we may think of how to better handle it
      on sched_pickcpu() side.
      
      MFC after:	1 month
      ef50d5fb
    • Randall Stewart's avatar
      tcp: Rack compressed ack path updates the recv window too easily · 1ca931a5
      Randall Stewart authored
      The compressed ack path of rack is not following proper procedures in updating
      the peers window. It should be checking the seq and ack values before updating and
      instead it is blindly updating the values. This could in theory get the wrong window
      in the connection for some length of time.
      
      Reviewed by: tuexen
      Sponsored by: Netflix Inc.
      Differential Revision: https://reviews.freebsd.org/D32082
      1ca931a5
    • Randall Stewart's avatar
      tcp: Two bugs in rack one of which can lead to a panic. · fd69939e
      Randall Stewart authored
      In extensive testing in NF we have found two issues inside
      the rack stack.
      
      1) An incorrect offset is being generated by the fast send path when a fast send is initiated on
         the end of the socket buffer and before the fast send runs, the sb_compress macro adds data to the trailing socket.
         This fools the fast send code into thinking the sb offset changed and it miscalculates a "updated offset".
         It should only do that when the mbuf in question got smaller.. i.e. an ack was processed. This can lead to
         a panic deref'ing a NULL mbuf if that packet is ever retransmitted. At the best case it leads to invalid data being
         sent to the client which usually terminates the connection. The fix is to have the proper logic (that is in the rsm fast path)
         to make sure we only update the offset when the mbuf shrinks.
      2) The other issue is more bothersome. The timestamp check in rack needs to use the msec timestamp when
         comparing the timestamp echo to now. It was using a microsecond timestamp which ends up giving error
         prone results but causes only small harm in trying to identify which send to use in RTT calculations if its a retransmit.
      
      Reviewed by: tuexen
      Sponsored by: Netflix Inc.
      Differential Revision: https://reviews.freebsd.org/D32062
      fd69939e
    • Ed Maste's avatar
      vt: bound buffer access in redraw optimization · dbc7ca59
      Ed Maste authored
      PR:		248628
      Reported by:	oleg
      Reviewed by:	cem, oleg (both earlier)
      Fixes:		ee97b233 ("Speed up vt(4) by keeping...")
      MFC after:	3 days
      Sponsored by:	The FreeBSD Foundation
      Differential Revision:	https://reviews.freebsd.org/D32059
      dbc7ca59
    • Michael Tuexen's avatar
      sctp: Cleanup stream schedulers. · 414499b3
      Michael Tuexen authored
      No functional change intended.
      
      MFC after:	1 week
      414499b3
    • Arnaud Ysmal's avatar
      LACP: Do not wait response for marker messages not sent · 0b92a7fe
      Arnaud Ysmal authored
      The error returned when a marker message can not be emitted on a port is not handled.
      
      This cause the lacp to block all emissions until the timeout of 3 seconds is reached.
      
      To fix this issue, I just clear the LACP_PORT_MARK flag when the packet could not be emitted.
      
      Differential revision:	https://reviews.freebsd.org/D30467
      Obtained from:		Stormshield
      0b92a7fe
    • Stephane Rochoy's avatar
      veriexec: Fix veriexec -i's confusion between loaded and locked states · 492bf4fd
      Stephane Rochoy authored
      Calling veriexec -i locked return the state of loaded and vice-versa.
      
      Differential revision:	https://reviews.freebsd.org/D30952
      Reviewed by:		sjg,imp
      Obtained from:		Stromshield
      492bf4fd
    • Stephane Rochoy's avatar
      sh: Add -o verify to use O_VERIFY when sourcing scripts · d2c23317
      Stephane Rochoy authored
      Add -o verify to sh to make it use O_VERIFY when
      sourcing scripts and reading profiles.
      
      Useful in conjunction with mac_veriexec to help protect at
      least some parts of the boot sequence, e.g., /etc/rc*.
      
      Differential revision:	https://reviews.freebsd.org/D30464
      Reviewed by:		jilles, sjg
      Obtained from:		Stormshield
      d2c23317
    • Hans Petter Selasky's avatar
      UPDATING: Fix spelling. · 90f6610b
      Hans Petter Selasky authored
      Submitted by:	gljennjohn@gmail.com
      Differential Revision:	https://reviews.freebsd.org/D31636
      Sponsored by:	NVIDIA Networking
      90f6610b
    • Kyle Evans's avatar
      kern: random: collect ~16x less from fast-entropy sources · 5e79bba5
      Kyle Evans authored
      Previously, we were collecting at a base rate of:
      
      64 bits x 32 pools x 10 Hz = 2.5 kB/s
      
      This change drops it to closer to 64-ish bits per pool per second, to
      work a little better with entropy providers in virtualized environments
      without compromising the security goals of Fortuna.
      
      Reviewed by:	#csprng (cem, delphij, markm)
      Differential Revision:	https://reviews.freebsd.org/D32021
      5e79bba5
    • Kyle Evans's avatar
      kern: random: drop read_rate and associated functionality · 6895cade
      Kyle Evans authored
      Refer to discussion in PR 230808 for a less incomplete discussion, but
      the gist of this change is that we currently collect orders of magnitude
      more entropy than we need.
      
      The excess comes from bytes being read out of /dev/*random.  The default
      rate at which we collect entropy without the read_rate increase is
      already more than we need to recover from a compromise of an internal
      state.
      
      Reviewed by:	#csprng (cem, delphij, markm)
      Differential Revision:	https://reviews.freebsd.org/D32021
      6895cade
    • Wojciech Macek's avatar
      hwpmc: fix performance issues · 7bc13692
      Wojciech Macek authored
      Differential revision:	https://reviews.freebsd.org/D32025
      
      Avoid using atomics as it_wait is guarded by td_lock.
      
      Report threshold calculation is done only if at least one PMC hook
      is installed
      
      Fixes:
      * avoid unnecessary branching (if frame != null ...)
        by having PMC_HOOK_INSTALLED_ANY
        condition on the top of them, which should hint
        the core not to execute speculatively anything
        which us underneath;
      * access intr_hwpmc_waiting_report_threshold cacheline
        only if at least one hook is loaded;
      7bc13692
    • Wojciech Macek's avatar
      pmc: intr pmc.soft(3) update · 319b1500
      Wojciech Macek authored
      Obtained from:		Semihalf
      Sponsored by:		Stormshield
      Reviewed by:		mhorne
      Differential revision:	https://reviews.freebsd.org/D32055
      319b1500
    • Baptiste Daroussin's avatar
      88741a40
    • Konstantin Belousov's avatar
      tests/sys/fs/fusefs/read.cc: fix build on powerpc64 · 3fcbde5e
      Konstantin Belousov authored
      There sig_atomic_t is shorter than void *.
      As result, it cannot keep pointer.
      
      Assigning to void * is actually safe for us in a signal handler.
      
      Reviewed by:	asomers
      Sponsored by:	The FreeBSD Foundation
      MFC after:	1 week
      Fixes:	4f917847
      Differential revision:	https://reviews.freebsd.org/D32064
      3fcbde5e