| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Approved by: so
|
| |
|
|
| |
Approved by: so
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
if the syscall muxes are used, up to two additional arguments
may be required. This means that the 8 required for mmap increases
up to 10 (for __syscall).
Sponsored by: Juniper Networks, Inc.
Approved by: so
Security: FreeBSD-EN-25:15.arm64
(cherry picked from commit 740b879c6ade531adebeba7cd2f261bbe650797f)
(cherry picked from commit 17d87881a363c160e7e8cdb252d0261214c1a50b)
|
| |
|
|
| |
Approved by: so
|
| |
|
|
| |
Approved by: so
|
| |
|
|
|
|
|
|
| |
Approved by: so
Security: FreeBSD-EN-25:11.ena
(cherry picked from commit 59b30c1a864ee8a22c2e9912301cb88674f714c9)
(cherry picked from commit a1685d25601ee7abfaf6d6a993932ae3318e070e)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch 0a33c047a443 introduced new values to
hw.ena.force_large_llq_header. The default value of 2 means no
preference, while 0 and 1 act as the previous false and true
respectively, which allowed forcefully setting regular or large LLQ.
There are 2 ways to force the driver to select regular LLQ:
1. Setting hw.ena.force_large_llq_header = 0 via sysctl.
2. Turning on ena express, which makes the recommendation by the FW to
be regular LLQ.
When the device supports large LLQ but the driver is forced to
regular LLQ, llq_config->llq_ring_entry_size_value is never initialized
and since it is a variable allocated on the stack, it stays garbage.
Since this variable is involved in calculating max_entries_in_tx_burst,
it could cause the maximum burst size to be zero. This causes the driver
to ignore the real maximum burst size of the device, leading to driver
resets in devices that have a maximum burst size (Nitro v4 and on. see
[1] for more information).
In case the garbage value is 0, the calculation of
max_entries_in_tx_burst divides by 0 and causes kernel panic.
The patch modifies the logic to take into account all use-cases and
ensure that the relevant fields are properly initialized.
[1]: https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html
Fixes: 0a33c047a443 ("ena: Support LLQ entry size recommendation from device")
Sponsored by: Amazon, Inc.
Differential Revision: https://reviews.freebsd.org/D50040
Approved by: so
Security: FreeBSD-EN-25:11.ena
(cherry picked from commit 56c45700f2ae15755358f2da8266247613c564df)
(cherry picked from commit 3f4a674a8ee430dec7c72c45ffe759eabefa7a1f)
|
| |
|
|
|
|
|
|
|
| |
From the upstream pull request merges:
#17340 b144b160b Fix 2 bugs in non-raw send with encryption
Obtained from: OpenZFS
Approved by: so
Security: FreeBSD-EN-25:10.zfs
|
| |
|
|
| |
Approved by: so
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This release incorporates the following bug fixes and mitigations:
- [CVE-2024-13176](https://www.openssl.org/news/vulnerabilities.html#CVE-2024-13176
- [CVE-2024-9143](https://www.openssl.org/news/vulnerabilities.html#CVE-2024-9143)
Release notes can be found at:
https://openssl-library.org/news/openssl-3.0-notes/index.html
Approved by: so
Security: FreeBSD-EN-25:07.openssl
Differential Revision: https://reviews.freebsd.org/D49296
Differential Revision: https://reviews.freebsd.org/D49297
(cherry picked from commit 0d0c8621fd181e507f0fb50ffcca606faf66a8c2)
(cherry picked from commit cb29db243bd09d16604435639ae43ef7af0ea254)
(cherry picked from commit d2a55e6a9348bb55038dbc6b727ab041085f22db)
(cherry picked from commit 0d61082e3c64a43f52ec5f1bf3d85671d97d9514)
|
| |
|
|
| |
Approved by: so
|
| |
|
|
| |
Approved by: so
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
File system specific *fid structures are copied into the generic
struct fid defined in sys/mount.h.
As such, they cannot be larger than struct fid.
This patch packs the structure and checks via a __Static_assert().
Approved by: so
Security: FreeBSD-SA-25:02.fs
Reviewed by: markj
MFC after: 2 weeks
(cherry picked from commit 4db1b113b15158c7d134df83e7a7201cf46d459b)
(cherry picked from commit 155987e2019089a5bd2eef77ed7bcc5cc26c362e)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
File system specific *fid structures are copied into the generic
struct fid defined in sys/mount.h.
As such, they cannot be larger than struct fid.
This patch packed the structure and checks via a __Static_assert().
Approved by: so
Security: FreeBSD-SA-25:02.fs
Reviewed by: markj
MFC after: 2 weeks
(cherry picked from commit bfc8e3308bee23d0f7836d57f32ed8d47da02627)
(cherry picked from commit 7a3a0402aeb626a7379addd344cbfd8900e83baa)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
File system specific *fid structures are copied into the generic
struct fid defined in sys/mount.h.
As such, they cannot be larger than struct fid.
This patch packs the structure and checks via a __Static_assert().
Approved by: so
Security: FreeBSD-SA-25:02.fs
Reported by: Kevin Miller <mas@0x194.net>
Reviewed by: olce, imp, kib, emaste
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D47879
(cherry picked from commit 205659c43d87bd42c4a0819fde8f81e8ebba068e)
(cherry picked from commit 54974e731f279941ef7aebd7d30ba2e9299a4056)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
syscallenter() has a slow path to handle syscall auditing and dtrace
syscall tracing. It uses AUDIT_SYSCALL_ENTER() to check whether to take
the slow path, but this macro also has side effects: it writes the audit
log entry. When systrace (dtrace syscall tracing) is enabled, this
would get short-circuited, and we end up not writing audit log entries.
Introduce a pure macro to check whether auditing is enabled, use it in
syscallenter() instead of AUDIT_SYSCALL_ENTER().
Approved by: so
Security: FreeBSD-EN-25:02.audit
Reviewed by: kib
Reported by: Joe Duin <jd@firexfly.com>
Fixes: 2f7292437d0c ("Merge audit and systrace checks")
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D48448
(cherry picked from commit f78fe930854cac6eed55859b45e0a7b5d87189d6)
(cherry picked from commit 4b9ba274d736de74676051c8f13e7d3dd536334b)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sockaddr passed to ktrcapfail() may be smaller than
sizeof(struct sockaddr), and the trailing bytes in the sockaddr
structure will be uninitialized, whereupon they get copied out to
userspace.
Approved by: so
Security: FreeBSD-SA-25:04.ktrace
PR: 283673
Reviewed by: jfree, emaste
Reported by: Yichen Chai <yichen.chai@gmail.com>
Reported by: Zhuo Ying Jiang Li <zyj20@cl.cam.ac.uk>
Fixes: 9bec84131215 ("ktrace: Record detailed ECAPMODE violations")
MFC after: 3 days
Differential Revision: https://reviews.freebsd.org/D48499
(cherry picked from commit 5b86888bae651e54ccc0adde0ed897ec1c1e0d45)
(cherry picked from commit 99d5ee8738a354e0d8f12453a82ed87e47bd62f1)
|
| |
|
|
|
|
|
|
|
| |
- Bump BRANCH to RELEASE
- Add the anticipated RELEASE announcement date
- Set a static __FreeBSD_version
Approved by: re (implicit)
Sponsored by: Amazon
|
| |
|
|
|
| |
Approved by: re (implicit)
Sponsored by: Amazon
|
| |
|
|
|
|
|
|
|
|
| |
Approved by: re (cperciva)
MFC after: 3 days
Reviewed by: ray
Differential Revision: https://reviews.freebsd.org/D47570
(cherry picked from commit 79af8f72b3aff993703778423e83320df0953a37)
(cherry picked from commit 3bcbd391dd7e1376ab7ad37e94f5b746abfc0591)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add sys/sytm.h for __diagused which unbreaks compilation of
drm-kmod 5.10-lts on main.
Sponsored by: The FreeBSD Foundation
Reported by: Evgenii Khramtsov
PR: 282479
Fixes: 5c92f84bb607
Approved by: re (cperciva)
(cherry picked from commit 9b2705121ba230bf71a1509cc928f0481dfbf31c)
(cherry picked from commit 06733ceca677b2d8ea2ae738bbb624d510fc9df8)
|
| |
|
|
|
| |
Approved by: re (implicit)
Sponsored by: Amazon
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Thu Sep 14 16:13:01 2023 +0000
vfs: don't provoke recycling non-free vnodes without a good reason
If the total number of free vnodes is at or above target, there is no
point creating more of them.
This commit was done as a performance optimization but ends up
causing slowdowns when doing operations on many files.
Approved by: re (cperciva)
Requested by: re (cperciva)
(cherry picked from commit ab05a1cf321aca0fe632c1ab40f68630b477422c)
(cherry picked from commit 2ca9c96dc0cf0d1f91b37346bce8fd0dd1639ddd)
|
| |
|
|
|
|
|
|
| |
PR: 282533
Approved by: re (cperciva)
(cherry picked from commit 580340dbdaaf372867e9ed3dd257430982753e5e)
(cherry picked from commit 92a9501b6be3d37a4eefcfbdda799b656ae146e8)
|
| |
|
|
|
|
|
| |
(cherry picked from commit f0c07fe3d0007a4499f81583a99598cd0a74d45b)
(cherry picked from commit c57dc755fa1a8bb0a4190f60df02b2bce5b8033c)
Approved by: re (cperciva)
|
| |
|
|
|
|
|
|
|
| |
Approved by: re (cperciva)
PR: 282389
MFC after: 3 days
(cherry picked from commit bab5e3d468305928e9e5cf1ca9efcee4c89f6a76)
(cherry picked from commit 5cc7196a81fe6924a2994a1efc31468ad045b0ce)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some iichid(4) child devices, currently hkbd(4) only, opens parent
device in their attach handlers. That breaks internal iichid(4) state
leading to rejecting any incoming data on software and hardware levels.
Fix it with adding of extra state check in iichid(4) attach handler.
Approved by: re (cperciva)
Reported by: many
Submitted by: trasz (initial version)
PR: 280290
MFC after: 3 days
(cherry picked from commit 018cb11cb7d412b031e1be681a6a19e734473f99)
(cherry picked from commit c53ec86f0ee97f07f80c0902b189c845bf448e7d)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to how the network stack needs to use mb_unmapped_to_ext() to
convert mbufs before passing them to an unsupported driver, if_bridge
needs to avoid passing M_EXTPG mbufs to interfaces that don't support
them. Thus, clear IFCAP_MEXTPG on the bridge if any member interfaces
don't handle unmapped mbufs.
Approved by: re (kib)
PR: 278245
Reviewed by: jhb, gallatin
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D47294
(cherry picked from commit 2bbfbf80d3bb828ac782c2d990a1fba0eb51e45a)
(cherry picked from commit 01a3c17d18bafbf4e76e9d77e8862525b50602e9)
|
| |
|
|
|
| |
Approved by: re (implicit)
Sponsored by: Amazon
|
| |
|
|
|
|
|
| |
(cherry picked from commit 518a1163d0aa73b26da1dd1a4bb186042ea3c66e)
(cherry picked from commit 0e8faabc270f89fbc54bbc118b2ebe2a38364375)
Approved by: re (cperviva)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Identify interfaces consistenly by the pair of the ifn pointer
and the index.
This avoids a use after free when the ifn and or index was reused.
Reported by: bz, pho, and others
(cherry picked from commit 523913c94371ab50a8129cbab820394d25f7a269)
(cherry picked from commit 331db93815afb49b01f269aeff0fe899acd47455)
Approved by: re (cperviva)
|
| |
|
|
|
|
|
| |
(cherry picked from commit 470a63cde4285ea4a317b0bba966514c11f4ed5b)
(cherry picked from commit e3f26ce52b71d4005e666ced22c0855dbc70b28e)
Approved by: re (cperviva)
|
| |
|
|
|
|
|
|
|
|
| |
Checking the interface name can not be done consistently, so
don't do it.
(cherry picked from commit bf11fdaf0d095fecca61fa8b457d06e27fae5946)
(cherry picked from commit 66628552a38751ed5c395858d1754660557674cd)
Approved by: re (cperviva)
|
| |
|
|
|
|
|
|
|
| |
Improve consistency, no functional change intended.
(cherry picked from commit d839cf2fbb47c52d5153fb366c51bd6f6a3dd0fd)
(cherry picked from commit 107704217b5733a2cae4e0fa1940f7ac66780f84)
Approved by: re (cperviva)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
xdr_void() should have type xdrproc_t, make it so.
Approved by: re (kib)
PR: 280514
Reviewed by: brooks, dim
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D47340
(cherry picked from commit a5d1cf5e362a2e3c3ebdf6d8f2b86658a6d0b9d6)
(cherry picked from commit b698c825f3b6699b278122da776bdfe5f360619f)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
386BSD provided a MD function sysbeep. This took two arguments (pitch
and period). Pitch was jammed into the PIT's divisor directly (which
means the argument was expected to sound a tone at '1193182 / pitch'
Hz). FreeBSD inherited this interface.
In commit e46598588587 (svn 177642, Mar 26 2008), phk changed this
function to take a tone to sound in hz. He converted all in-tree
instances of 1193182 / hz to just hz (and kept the few misguided folks
that passed hz directly unchanged -- this was part of what motivated the
change). He converted the places where we pre-computed the 8254 divisor
from being pitch to 1193182 / pitch (since that converts the divisor to
the frequency and the interfaces that were exposed to userland exposed
it in these units in places, continuing the tradition inherited from SCO
System V/386 Unix in spots).
In 2009, Ed Shouten was contracted by the FreeBSD Foundation to write /
finish newcons. This work was done in perforce and was imported into
subversion in user/ed/newcons in revision 199072
(https://svnweb.freebsd.org/base?view=revision&revision=199072) which
was later imported into FreeBSD by ray@ (Aleksandr Rybalko).
From that earliest import into svn import to this date, we ring the bell
with:
sysbeep(1193182 / VT_BELLPITCH, VT_BELLDURATION);
where VT_BELLPITCH was defined to be 800. This results in a bell
frequency of 1491Hz, more or less today. This is similar to the
frequency that syscons and pcvt used (1493Hz and 1500Hz respectively).
This in turn was inherited from 386BSD, it seems, which used the hard
coded value 0x31b which is 795 -> 1500Hz.
This '800' was intended to be the bell tone (eg 800Hz) and this
interface was one that wasn't converted. The most common terminal prior
to the rise of PCs was the VT100, which had an approximately 800Hz
bell. Ed Shouten has confirmed that the original intent was 800Hz and
changing this was overlooked after the change to -current was made.
This restors that original intent and makes the bell less obnoxious in
the process.
Reviewed by: des, adrian
Differential Revision: https://reviews.freebsd.org/D32594
Sponsored by: Netflix
(cherry picked from commit ba48d52ca6c867559156dd916631f9ac47abe80f)
This change was accidentally reverted in 80f21bb039ce.
(cherry picked from commit 2416be588ea113cc06b924ed85861ed3bc391fe0)
(cherry picked from commit 1c9f1cb4f0a71bef37796a8ba139b86cc716ee88)
Approved by: re (cperciva)
|
| |
|
|
|
|
|
|
|
| |
'acpi_if.h' was accidentally omitted from the module Makefile; add it.
Approved by: re (kib)
Fixes: 9709bda03cd0
(cherry picked from commit bb8b3b1741188ab284e8b48ec367961a480421cb)
(cherry picked from commit 393bbd23b3446bb4ac4924f7e1c98bbdcff4455d)
|
| |
|
|
|
|
|
|
|
|
| |
Approved by: re (kib)
Fixes: 9709bda03cd0 ("GPIO: Add ACPI _AEI support")
Pointy-hat to: cperciva
Sponsored by: Amazon
(cherry picked from commit 6540ac118473dde29cb02f786c79c64f73834ca1)
(cherry picked from commit 5a53843aef490bda32397e80b3fb600e802b461c)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes to acpi_gpiobus.c handle discovering and parsing the _AEI
objects and storing necessary data in device ivars. A new gpioaei.c
file implements the device, which simply requests an interrupt when
the pin is triggered and invokes the appropriate _Exx or _Lxx ACPI
method.
This makes the GPIO "power button" work on arm64 Graviton systems,
allowing EC2 "Stop"/"Reboot" instance calls to be handled cleanly.
(Prior to this change, those requests would time out after 4 minutes
and the instance would be forcibly killed.)
Reviewed by: imp, andrew, Ahmad Khalifa
Approved by: re (kib)
MFC after: 3 days
Sponsored by: Amazon
Differential Revision: https://reviews.freebsd.org/D47253
Co-authored-by: Andrew Turner <andrew@FreeBSD.org>
(cherry picked from commit 9709bda03cd0f20eba0ba4276fc3c2e06354a54f)
(cherry picked from commit c2cd78d9446ebe79accf6c1862230dfbe7276525)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[MFC note: This is not a direct cherry-pick due to API changes in HEAD
which are not present in stable/14.]
We need to call into INTRNG to activate all interrupts on platforms that
use it. Currently, interrupts are only activated in the nexus drivers for
INTRNG platforms, but this does not handle other bus devices such as
gpiobus that manage their own IRQ space.
Reported by: cperciva
Reviewed by: cperciva, jhb
Approved by: re (kib)
Sponsored by: Arm Ltd
Differential Revision: https://reviews.freebsd.org/D47282
(cherry picked from commit c85855a72db9f9d7b4326b676241e1dffabf0fae)
(cherry picked from commit c54bdf84d5fb0b2c1923179fd30812ee68aaf423)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GPIO interrupts work just fine and will be used shortly. We still
do not support GPIO_INTR_SHAREABLE however, so leave that within
the NOT_YET scope.
Reviwed by: andrew
Approved by: re (kib)
MFC after: 1 week
Sponsored by: Amazon
Differential Revision: https://reviews.freebsd.org/D47251
(cherry picked from commit 2d4219919a48aa6d67ae62e2b8859ffe3b035bd2)
(cherry picked from commit 1f6941760746367704c9f1fa730a00b99d4d46b2)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows acpi_gpiobus to override the method and fall back to the
generic gpiobus_read_ivar function if needed.
Reviewed by: andrew
Approved by: re (kib)
MFC after: 1 week
Sponsored by: Amazon
Differential Revision: https://reviews.freebsd.org/D47250
(cherry picked from commit bc0d10d01c3c69004d600e14d53cd0dceffe4b09)
(cherry picked from commit fffdfe2f6770946bb5d5204df0a97105e1dceccb)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AWS Graviton [1234] systems have a bug in their ACPI where they mark
the PL061's GPIO pins as needing to be configured in PullUp mode (in
fact the PL061 has no pullup/pulldown resistors); this flag needs to
be removed in order for _AEI objects to be handled on these systems.
Reviewed by: Ali Saidi
Approved by: re (kib)
MFC after: 1 week
Sponsored by: Amazon
Differential Revision: https://reviews.freebsd.org/D47239
(cherry picked from commit 2f3f867ac6dd7ff3769366b828b79c44b38828e1)
(cherry picked from commit 5fa51c3653b14b364e26a4cce2733c7be6ee7721)
|
| |
|
|
|
|
|
|
|
|
|
| |
This is the GPIO_INTR_EDGE_* flags, just as a convenience to let code
test flags for interrupt edginess.
Approved by: re (kib)
Sponsored by: Amazon
(cherry picked from commit f6197f2bc05b5a8df260cbf55283fddf7c76fec4)
(cherry picked from commit bebff69739ed5d9c6bbc7796a981da867420f77e)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ACPI sleep states are only implemented on x86 systems, so having the
ACPI power button attempt to enter "S5" (or other state as configured
via the hw.acpi.power_button_state sysctl) is not useful.
On non-x86 systems, implement the power button with a call to
shutdown_nice(RB_POWEROFF)
to shut down the system.
Reviewed by: Andrew
Tested on: Graviton 2
Approved by: re (kib)
MFC after: 2 weeks
Sponsored by: Amazon
Differential Revision: https://reviews.freebsd.org/D47094
(cherry picked from commit f41ef9d80b3d272e08dd9e2ea3c1d8d3f2818066)
(cherry picked from commit e177e64294556bdece642442d6691523a4294b67)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Right now flags is set to 0 before this "=" -> "|=" change, but it will
matter when the NOT_YET section above becomes effective.
Approved by: re (kib)
MFC after: 2 weeks
Sponsored by: Amazon
(cherry picked from commit c808132731aa999947f4f7810157d7d8d9aaf61e)
(cherry picked from commit 7c8f273bfba28d9d55ada94c80feb3ba97c53758)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This currently only implements the address space handler and attempts to
configure pins with flags obtained from ACPI.
Reviewed by: wulf
Approved by: re (kib)
MFC after: 1 month
Pull Request: https://github.com/freebsd/freebsd-src/pull/1359
(cherry picked from commit 92adaa5862d5ea94318a011e0618622d0fb72521)
(cherry picked from commit 14887d2c869ad47d5921fc9aa07e891a38950121)
|
| |
|
|
|
|
|
|
|
| |
Update from PRERELEASE to BETA1
Switch pkg(8) configuration to use the quarterly repository
Bump __FreeBSD_version
Approved by: re (implicit)
Sponsored by: Amazon
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows iavf to load on E830 devices since those devices place their MSI-X
BAR at a different location than in previous 800 series products.
Signed-off-by: Eric Joyner <erj@FreeBSD.org>
Sponsored by: Intel Corporation
Differential Revision: https://reviews.freebsd.org/D46952
(cherry picked from commit e53a21abdf2953714e44e3c54b4bb78557cb096c)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Features:
* Add support for device request reset message over AENQ
* Support LLQ entry size recommendation from device
* Support max large LLQ depth from the device
* Expand PHC infrastructures
* Configuration notification support
Bug Fixes:
* Fix leaking ifmedia resources on detach
* Fix netmap socket chain unmapping issue
* Properly reinit netmap structs upon sysctl changes
* Correctly count missing TX completions
Minor Changes:
* Add reset reason for corrupted TX/RX completion descriptors
* Add reset reason for missing admin interrupts
* Improve reset reason statistics
* Update licenses
Approved by: cperciva (mentor)
Sponsored by: Amazon, Inc.
(cherry picked from commit ce4cc746bb4171a131ab9099947a500c0de18ff4)
|