Age | Commit message (Collapse) | Author |
|
Ok deraadt@ guenther@
|
|
|
|
|
|
ok deraadt@
|
|
re-creating the original (2 weeks ago) order of last-minute-disk-parking
needs a different approach, hmm.
|
|
3055.
|
|
|
|
|
|
failure modes. Also, pack the code a little bit, easier to read.
|
|
OK mpi@
|
|
OK mpi@
|
|
OK mpi@
|
|
OK kettenis@
|
|
ASCII data should not include trailing NUL but we MUST delete trailing
NULs on receiving.
Jan Vlach ( janus AT volny.cz) reported that Microsoft DHCP server
sends the domain name option with a trailing NUL which the installer
put into /etc/myname as a trailing ^@ which smtpd does not like.
Fix some whitespace while here.
Input & OK millert
|
|
bug reported by giovanni@
OK giovanni@
|
|
ok guenther@ rob@
|
|
|
|
than scheduling an acpi thread
|
|
|
|
and restart the suspend all over again. This was previously done by issuing
a task to the acpi thread, but this is simpler.
(I want to try to duplicate these tests earlier in the resume path...)
|
|
able to react to this suitably.
|
|
attached audio device, i.e. audio0. This approach does not work well
while using additional audio devices equipped with physical volume keys
since those would only affect the volume of audio0.
Instead, correlate audio and ucc devices attached over USB in order to
adjust the volume of the correct audio device. This is done by passing a
cookie from the common point of attachment which is later used to
correlate the audio and wskbd device.
The same approach could be adopted for audio and wskbd devices attaching
on a different bus. Keep in mind that it's of importance to make use of
and increment the same global cookie identifier to avoid collisions.
Makes the volume keys on my Logitech G435 Headset do the right thing.
ok ratchov@
|
|
unused but intended to be used to correlate audio and wskbd devices.
ok ratchov@
|
|
consistently means we do the check in pf_rule_copyin() so both
DIOCADDRULE and DIOCCHANGERULE have the prio values checked. this in
turn prevents invalid prio values getting set on a rule via
DIOCCHANGERULE.
this was caught by a kassert in the ifq priq code firing.
Reported-by: syzbot+a8f8e24a44b441e71d93@syzkaller.appspotmail.com
ok sashan@
|
|
ok jca@
|
|
ok jca@
|
|
ok jca@
|
|
if an open tun (or tap) device is destroyed via the clone destroy
ioctl (eg, like what ifconfig destroy does), there is a window while
the open device is being revoked on the vfs side that a third thread
can come and open it again. this in turn triggers a kassert in the
ifconfig destroy path where it expects the
device to be closed.
fix this by having tun_dev_open check for the TUN_DEAD flag that
the destroy function sets. this still relies on the kernel lock for
serialisation.
Reported-by: syzbot+5df2ad232f5f8b671442@syzkaller.appspotmail.com
ok visa@
|
|
|
|
|
|
the big change is removing the integration with and reliance on
bridge(4) for learning vxlan endpoints. we have the etherbridge
layer now (which is used by veb, nvgre, bpe, etc) so vxlan can
operate independently of bridge(4) (or any other driver) while still
dynamically learning about other endpoints.
vxlan now uses the udp socket upcall mechanism to receive packets.
this means it actually creates and binds udp sockets to use rather
adding code in the udp layer for stealing packets from the udp
layer.
i think it's also important to note that this adds loop prevention
to the code. this stops a vxlan interface being used to transmit a
packet that was encapsulated in itself.
i want to clear this out of my tree where it's been sitting for
nearly a year. noone seems too concerned with the change either
way.
ok claudio@
|
|
Ok deraat@
|
|
ok kettenis@
|
|
with AML parsing outside the acpi thread, the locking-release dance
around wsdisplay_{suspend,resume} can be removed
ok kettenis
|
|
ok deraadt@
|
|
reset the MD state before bailing out. New MD function sleep_abort()
does that.
|
|
Like set-clipboard and allow-rename it is safer to forbid this by
default.
|
|
query.
|
|
Fixes my com0 issues after zzz and ZZZ.
OK kettenis@ miod@
|
|
|
|
The (known) lock order reversals which now occur more reliably and much
earlier on WITNESS boots with this diff knock out syzcaller reports since
syzcaller stops at the first "crash report":
https://syzkaller.appspot.com/bug?id=81b39e970cd2eb21b97d1b31746c693e300fd2dd
|
|
ok miod@
|
|
|
|
OK dlg@
|
|
|
|
okay afresh1@
|
|
have a state once I'm past the initial locking
|
|
spotted by HARUYAMA Seigo
|
|
tun_dev_open and tun_dev_close were being optmistic.
|
|
it only works on struct ifnet data, so passing ifp makes it clearer
what's actually being manipulated. also fix tun_dev_open so
tun_link_state is called before if_put instead of immediately after.
|