Age | Commit message (Collapse) | Author |
|
Tested on rockpro64.
ok sthen@
|
|
sigcoderet label must point directly after the svc instruction, because the
sigreturn() checks it as SROP mitigation, so place the sled after the label.
tested by naddy
|
|
for SYS_exit and SYS_sigreturn in the sigtramp"; init has trouble
spawning processes.
|
|
and SYS_sigreturn in the sigtramp. As these control-flow into a jump
or process termination, we never do the +8 dance over the
instructions, however the speculation prevention (once these nops are
replaced with a speculation barrier) is required.
oversight noticed by Anthony Steinhauser.
|
|
asked for more oks; my bad!
|
|
operating on the process structure and issuing signals. This is similar
to what sigio_setown() already does.
With this in place, the pipe subsystem is no longer required to grab the
kernel lock before calling pgsigio().
ok visa@
|
|
As vlan instances obtained from the lists are passed to if_vinput(), which
may sleep (with PF locking enabled), we only traverse the vlan lists inside
the SMR critical section, and keep the existing reference counting in place.
ok visa@ sashan@
|
|
operations. Since the type of f_flag must change in order to use the
atomic(9) API, reorder the struct in order to avoid padding; as pointed
out by tedu@.
ok mpi@ visa@
|
|
this means a route message is sent when the interface is closed and
goes down, but also causes another route message to be sent when
the interface comes up on the next open. this is important for
things like ospfd and the ospfd regress test because they want to
know when link comes up.
the regression was pointed out by bluhm, who also helped me isolate
the problem.
|
|
Noticed and reported by Adam Steen.
|
|
this restores restores returning POLLERR when the device is gone.
ENXIO doesn't make much sense as part of a pollfd revents field.
|
|
toward MP-safety.
OK mpi@, anton@
|
|
Requested by and OK mpi@
OK anton@
|
|
|
|
Tested by krw@, anton@
OK mpi@, anton@
|
|
Using different fields to remember in which runqueue or sleepqueue
threads currently are will make it easier to split the SCHED_LOCK().
With this change, the (potentially boosted) sleeping priority is no
longer overwriting the thread priority. This let us get rids of the
logic required to synchronize `p_priority' with `p_usrpri'.
Tested by many, ok visa@
|
|
Whenever a "mixer" control is changed by a program or with volume
keys, its index may be read from the /dev/audioctlN device using
the read(2) syscall. Only one reader at a time is allowed.
|
|
klist_invalidate() detaches knotes from the list and rewires them
synchronously so that the original filterops routines do not get
called after the invalidation.
OK anton@, mpi@
|
|
into the brightness-levels array.
|
|
calling the ACPI methods. On some machines, like my X395,
those ACPI methods don't allow changing the brightness, so
this allows acpivout(4) to e.g. use amdgpu(4)'s code.
In comparison to the previously committed and backed out
version we now schedule the brightness change on the ACPI
task queue so that we don't run into any recursive locking
issues. Additionally the diff has been modified according
to the recent commit where we make sure that a 5% brightness
change does not result in the same brightness level.
ok jcs@ kn@
|
|
From Sam Bobroff
6fab6dbff4a5843b8f44f87a2454450961c1f0bc in linux 4.19.y/4.19.99
62d91dd2851e8ae2ca552f1b090a3575a4edf759 in mainline linux
|
|
From Jani Nikula
e34d8d2b2e2f49d1aa933a1e5f15d3e9ee9aa54b in linux 4.19.y/4.19.99
bf3f5e98559360661a3d2af340d46522512c0b00 in mainline linux
|
|
From Noralf Tronnes
6c5df6f63e8f98fe89c41c879385105bd0952248 in linux 4.19.y/4.19.99
6e3f17ee73f7e3c2ef0e2c8fd8624b2ece8ef2c9 in mainline linux
|
|
From Noralf Tronnes
66779aa306b37b3789e7acae0b60017b7c3a51d3 in linux 4.19.y/4.19.99
6e1490cf439aa86b104e5124c36275b964238e1f in mainline linux
|
|
From Lyude Paul
035e304f95c3b3ed11ef8a0de48269ef4faad2e7 in linux 4.19.y/4.19.99
c54c7374ff44de5e609506aca7c0deae4703b6d1 in mainline linux
|
|
like USB only use the former and bpf_iflist was otherwise retaining
references to a freed bpf_if.
ok sashan
|
|
is invoked. This enables threads to continue gathering events without
interruption when another thread starts or stops recording.
OK mpi@
|
|
Tested by me; Hardware provided by Titus Richartz and Theo Richartz, thanks!
|
|
|
|
|
|
changed in r1.40 but the function itself was missed. Unbreaks i386 build -
no other arch enables adv(4).
|
|
Tested by and ok jcs@
|
|
|
|
obvious by consistently using the variable names and idiom of
sdminphys.
No functional change.
|
|
|
|
|
|
Add a KASSERTMSG() to check that strategy functions didn't screw
b_resid up too much.
ok beck@ tedu@
|
|
|
|
it's not there. This allows pwmbl(4) to attach and work on the Pinebook
Pro.
|
|
in RFC8622; ok job@
|
|
ok jsg@
|
|
is good enough to enable the Pinebook Pro's panel.
It would be nice to make use of the DRM's BSD-licensed panel code,
which has an extensive list of panels and its settings.
ok kettenis@
|
|
|
|
intended for shm/fd passing, but for programs that may otherwise like
filesystem access.
ok beck deraadt kettenis
|
|
|
|
|
|
no function change.
|
|
|
|
|
|
inducing. Rename scsi_adapter member 'scsi_minphys' to 'dev_minphys'
to reflect what it is supposed to do. Use consistent naming convention
(<dev>_minphys) for the actual device functions.
No functional change.
|