Fix Tx performance on iwx(4) BZ devices.
BZ devices need to be told how long the MAC header is in the offload_assist
field of the Tx command, even if no offloading features are being used.
Found by chance while browsing iwlwifi driver git logs.
See linux.git commit af8bfc7e38a7ad4f8e1663de7ab1463e644050b2
When pledged, if a process receives a bad descriptor the receiver should
not be killed. The EPERM approach used for other conditions is good enough.
from deraadt@; Report from Henry Ford
this is errata/7.7/028_recvfd.patch.sig
When pledged, if a process receives a bad descriptor the receiver should
not be killed. The EPERM approach used for other conditions is good enough.
from deraadt@; Report from Henry Ford
this is errata/7.8/022_recvfd.patch.sig
Make iwx(4) only attach to BZ devices which have RF type GF (wifi 6e).
PCI vendor/product IDs can be shared between Intel wifi 6e and wifi 7 devices.
Wifi 7 devices need different firmware and probably a new driver.
Avoid matching them.
Bad match on a wifi 7 device reported by Jesper Wallin.
pfctl(8) parser must not ignore error from pfctl_optimize_ruleset().
Ignoring the error may cause pfctl(8) to load inconsistent ruleset
preventing pf(4) to enforce desired policy.
Issue reported and fix suggested by berts _from_ fastmail _dot_ com
'Looks good.' @deraadt
sync iwx(4) RX descriptor status field with firmware layout
Same change was made in iwlwifi about 6 years ago.
See linux.git commit e365e7de63e5b612d94fb433e38d9414de811f7d
This matters to us now that we started looking at Rx status bits
beyond 16 bits in order to check for duplicate subframes in A-MPDUs.
Found by Coverity (CID 1670294)
pointed out by and ok jsg@
Fix support for some older iwx(4) devices broken by changes for BZ support.
Keep hardware revision info sent to firmware intact for older devices.
BZ devices store parts of hardware revision information in a new place.
I accidentally changed the information sent to older devices, which broke
firmware loading on a subset of AX201/AX210 devices.
Reported to me by several people, thanks!
This fix is based on a patch by David Leadbeater.
xargs(1): bump posix spec to 2024
The spec now documents -0 and -r.
In addition, the spec notes that specifying both -0 and -E are mutually
exclusive, leaving the actual behavior unspecified.
ok deraadt@, guenther@ on the spec version bump
ok millert@ on documenting the interaction between -0 and -E
rfc3779 regress: add an actual range
This improves the test coverage of make_addressRange() where there is an
annoyance with unused bits in the RFC 3779 ASN.1 encoding versus trailing
ones in the network encoding that the X509v3_addr_add_range() API expects.
When pledged, if a process receives a bad descriptor the receiver should
not be killed. The EPERM approach used for other conditions is good enough.
Report from Henry Ford
this will be errata 7.8/022_recvfd.patch and 7.7/028_recvfd.patch
drm/sched: Fix kernel-doc warning for drm_sched_job_done()
From Yujie Liu
da09dfc90cb7ed1ab40d675234382f151eeb0563 in linux-6.18.y/6.18.17
61ded1083b264ff67ca8c2de822c66b6febaf9a8 in mainline linux
drm/syncobj: Fix handle <-> fd ioctls with dirty stack
From Julian Orth
7196a1ff7b9a2ab6d973fe3c1dfc426d8d8ed4d2 in linux-6.18.y/6.18.17
2e3649e237237258a08d75afef96648dd2b379f7 in mainline linux
drm/amd/display: Use GFP_ATOMIC in dc_create_stream_for_sink
From Natalie Vock
0381584929791c4b989fb0a36a466ae20aea1608 in linux-6.18.y/6.18.17
28dfe4317541e57fe52f9a290394cd29c348228b in mainline linux
drm/i915/dp: Fix pipe BPP clamping due to HDR
From Imre Deak
9498fa25a0b0d8c095ce3d1f15d7864228692822 in linux-6.18.y/6.18.17
fe26ae6ac8b88fcdac5036b557c129a17fe520d2 in mainline linux
drm/i915/dp: Fail state computation for invalid DSC source input BPP values
From Imre Deak
99f617ea2ff017b0ba10d5371d83345331091afa in linux-6.18.y/6.18.17
338465490cf7bd4a700ecd33e4855fee4622fa5f in mainline linux
drm/amd: Fix hang on amdgpu unload by using pci_dev_is_disconnected()
From Mario Limonciello
378dff71efddd15f34124bf9d7c98cd69cd05286 in linux-6.18.y/6.18.17
f7afda7fcd169a9168695247d07ad94cf7b9798f in mainline linux
drm/amdgpu: Fix error handling in slot reset
From Lijo Lazar
73e8bdf14248136459753252a438177df7ed8c7c in linux-6.18.y/6.18.17
b57c4ec98c17789136a4db948aec6daadceb5024 in mainline linux
drm/amdgpu: Fix locking bugs in error paths
From Bart Van Assche
5c42d9f8b004905eb441f0eab34662bdacf3192f in linux-6.18.y/6.18.17
480ad5f6ead4a47b969aab6618573cd6822bb6a4 in mainline linux
drm/amdgpu: Unlock a mutex before destroying it
From Bart Van Assche
39ae59e5c1d880176c41ecc2694e0ae81335079d in linux-6.18.y/6.18.17
5e0bcc7b88bcd081aaae6f481b10d9ab294fcb69 in mainline linux
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
From Tvrtko Ursulin
1753f5f81ab60a553287f9ee659a6ac363adf8d7 in linux-6.18.y/6.18.17
7b7d7693a55d606d700beb9549c9f7f0e5d9c24f in mainline linux
drm/client: Do not destroy NULL modes
From Jonathan Cavitt
4e3ca5f82346cc23c0a71f1ceb006115ff6b0745 in linux-6.18.y/6.18.17
c601fd5414315fc515f746b499110e46272e7243 in mainline linux
drm/fourcc: fix plane order for 10/12/16-bit YCbCr formats
From Simon Ser
cd2713a37336d839027f60ecb3964f1c595991bf in linux-6.18.y/6.18.17
e9e0b48cd15b46dcb2bbc165f6b0fee698b855d6 in mainline linux
xargs: Make the -0 option override -E.
POSIX 1003.1-2024 states that -0 and -E are mutually exclusive, but
leaves unspecified the actual behavior when both are specified.
Unlike GNU xargs, we don't emit a warning when both -0 and -E are
given. OK daniel@
