Specify the correct "read" and "write" bits to the NVMMU based on the
opcode of the NVMe command. Drop the opcode itself, since it isn't needed.
This allows us to drop the magic "null check" bit that is no longer
supported by the firmware that Apple ships with newer macOS releases.
Based on work done by Sven Peter over at Asahi Linux.
ok jmatthew@
Prevent read buffer overflow in verbose debug logging.
When we receive more than 8 nameservers in a DHCP lease we would
overread the nameservers buffer because the loop was not bounded by
items in the array but the whole size.
Pointed out by Stuart Thomas some time ago, thanks!
isakmpd: Handle malformed MONITOR_BIND message
Using a stack allocated sockaddr_storage avoids the malloc(3)
entirely. Add length checks for the payload sent by the child.
When a malicious child sends us a malformed message the privsep
protocol is out of sync. Thus terminate gracefully with log_fatalx().
While there, attribute log_fatalx() with __dead.
Reported by Shibo, Hugo Systopia Team
ok markus@ tb@ deraadt@
disable dynamic power gating on Panther Lake and later
described in Intel changes as known to cause hangs
tested on 0x57b3 / E1000_DEV_ID_PCH_PTP_I219_LM25
partly from Intel's DPDK driver
ok jmatthew@
change K1 exit timeout on Meteor Lake and later
without this my Panther Lake machine could not receive non-broadcast packets
tested on 0x57b3 / E1000_DEV_ID_PCH_PTP_I219_LM25 and
0x550b / E1000_DEV_ID_PCH_MTP_I219_V18
partly from Intel's DPDK driver
ok jmatthew@
match Panther Lake and Wildcat Lake
tested on 0x57b3 / E1000_DEV_ID_PCH_PTP_I219_LM25
needs workarounds coming in another commit to be useable
ok jmatthew@
fq_codel: fix CoDel drop scheduling
Use drops - 1 as the codel_intervals index; the table starts at interval
/ sqrt(1) while cd->drops is one-based. Assert non-zero.
Exclude the candidate packet from the non-starvation backlog check; the
decision is about the backlog remaining after dequeue.
Enter dropping when now equals cd->start, not only when it exceeds it.
OK sashan@
revert 'drm/amd/display: Fix backlight max_brightness to match exported range'
jmc@ reports this 6.18.42 change caused a very dim display on boot and with
display.brightness values of 97-100 on a Dell Inspiron 5505
it looks like this patch will be reverted in linux stable branches
https://gitlab.freedesktop.org/drm/amd/-/work_items/5562
relayd: remove dead backup flag and token
The idea behind it was good, but it was never fully and properly implemented.
It's better to remove it before reimplementing the concept from scratch
and doing it right. Reading the man page makes it a little easier.
OK kirill@
relayd: check proc_compose return values
Fatal on config, setup, and startup imsg send failures. Inconsistent
state means we can't recover.
Warn on per-request responses and sync messages. A single dropped
message shouldn't kill the whole process.
OK kirill@
Protect the IPsec TDB replay counter with mutex.
Put all tdb_rpl read, write and increment under tdb_mtx. Although
shared net lock and kernel lock should be enough for now, we want
to move towards fine grained locking. Mark tdb_rpl and tdb_seen
as MP safe.
The wrap-around check in ah_output() is not atomic with the increment
code and would not work. As tdb_rpl is 64 bit nowadays, it cannot
warp. Better remove the useless tdb_rpl == 0 check than making it
MP safe.
OK deraadt@