| Age | Commit message (Collapse) | Author |
|---|
|
Read-only access to local `clkinfo' filled with immutable data.
ok bluhm
|
|
If an interrupt-generating device does not have an interrupt-parent
property, its interrupt parent is assumed to be its devicetree
parent.
Implement this aspect of the spec in the same way as Linux does by not
just looking at the immediate parent but keep on walking up the tree
until we hit a node with an "interrupt-controller" property or a node
that has an "interrupt-parent" property.
similar diff as committed for arm64 a couple of days ago
ok jca@
|
|
Instead of the KERNEL_LOCK use the ps_mtx for most operations.
If the ps_klist is modified an additional global rwlock (kqueue_ps_list_lock)
is required. This includes the knotes with NOTE_FORK and NOTE_EXIT since
in either cases a ps_klist is changed. In the NOTE_FORK | NOTE_TRACK case
the call to kqueue_register() can sleep this is why a global rwlock is used.
Adjust the reaper() to call knote_processexit() without KERNEL_LOCK.
Double lock idea from visa@
OK mvs@
|
|
OK miod@ kettenis@
|
|
Sure deraadt@
|
|
this is avoids passing excessively large values to timeout_add_nsec.
Reported-by: syzbot+f650785d4f2b3fe28284@syzkaller.appspotmail.com
|
|
|
|
you can only fit a couple of nanonseconds into an int, which limited
the usefulness of the api. worse, if a large nsec value was passed
in it could be cast to a negative int value which tripped over a
KASSERT at the top of timeout_add that ends up being called. avoid
this footgun by working in the bigger type and doing the same range
checks/fixes for other timeout_add wrappers.
ok claudio@ mvs@
|
|
microboottime() and following binboottime() are mp-safe and `mb' is
local data.
ok bluhm
|
|
ok patrick@
|
|
ok jca@, mlarkin@
|
|
ok phessler@
|
|
Sending IPv6 fragments over a bridge with pf did not work. During
input pf reassembles the packet, and at bridge output it should be
refragmented. This is only done for PF_FWD direction, but bridge(4)
and veb(4) called pf_test() with PF_OUT argument.
OK sashan@
|
|
Add corresponding cases to the kern_sysctl() switch and unlock read-only
variables from `kern_vars'. Unlock KERN_SOMAXCONN and KERN_SOMINCONN
which are atomically read-only accessed only from solisten().
ok kettenis
|
|
If an interrupt-generating device does not have an interrupt-parent
property, its interrupt parent is assumed to be its devicetree
parent.
Implement this aspect of the spec in the same way as Linux does by not
just looking at the immediate parent but keep on walking up the tree
until we hit a node with an "interrupt-controller" property or a node
that has an "interrupt-parent" property.
same diff as committed for arm64 yesterday
ok patrick@
|
|
ok bluhm
|
|
|
|
|
|
The only thing it does is error because of a check added in sockargs() in
uipc_syscalls r1.155. As guenther pointed out, this may have been added
because of a misreading of the last sentence of the first paragraph of the
connect(2) manual.
Instead of erroring, this will keep listening if -k is given and otherwise
it will close the socket and exit with success.
ok guenther jeremy
|
|
elevated to errors using the -Wl,--fatal-warnings option.
ok robert@
|
|
From Imre Deak
12880cc086deef91e62e2f010750087a3c23fae3 in linux-6.6.y/6.6.44
509580fad7323b6a5da27e8365cd488f3b57210e in mainline linux
|
|
From Imre Deak
a90e900f71da23a354e9d17f1dc0c654d0ae9ceb in linux-6.6.y/6.6.44
d13e2a6e95e6b87f571c837c71a3d05691def9bb in mainline linux
|
|
From Ma Ke
e150f0171c0c0c45a373a658358c51c940ed4fd9 in linux-6.6.y/6.6.44
df65aabef3c0327c23b840ab5520150df4db6b5f in mainline linux
|
|
From ZhenGuo Yin
323790535237927e1b6a7bc35ddf662c6e7c25cc in linux-6.6.y/6.6.44
5659b0c93a1ea02c662a030b322093203f299185 in mainline linux
|
|
From Wayne Lin
e290feb8b749a06b93ed01d4cf66567cbdf0e85d in linux-6.6.y/6.6.44
d63d81094d208abb20fc444514b2d9ec2f4b7c4e in mainline linux
|
|
From Alex Deucher
9d74e50098492e89f319ac6922db3c2062f69340 in linux-6.6.y/6.6.44
a03ebf116303e5d13ba9a2b65726b106cb1e96f6 in mainline linux
|
|
From Nitin Gote
05c0fb20ca3e000a7e966584845731ba4fc950da in linux-6.6.y/6.6.44
65564157ae64cec0f527583f96e32f484f730f92 in mainline linux
|
|
From Sung Joon Kim
4ccd37085976ea5d3c499b1e6d0b3f4deaf2cd5a in linux-6.6.y/6.6.44
4ab68e168ae1695f7c04fae98930740aaf7c50fa in mainline linux
|
|
From Tim Van Patten
6d72626808325c1986cbf90b0ce27a59b4291876 in linux-6.6.y/6.6.44
1446226d32a45bb7c4f63195a59be8c08defe658 in mainline linux
|
|
From Friedrich Vock
67b4592a7d74e57a5a0929eaf3ae30414ebd39ae in linux-6.6.y/6.6.44
0cdb3f9740844b9d95ca413e3fcff11f81223ecf in mainline linux
|
|
From Lijo Lazar
ae1dd0a379e41db7d4773880e6918948668ef3ad in linux-6.6.y/6.6.44
ce798376ef6764de51d8f4684ae525b55df295fa in mainline linux
|
|
From Lijo Lazar
0af2e5cb74514877326448becf40365b073b44e2 in linux-6.6.y/6.6.44
b6420021e17e262c57bb289d0556ee181b014f9c in mainline linux
|
|
From Mukul Joshi
cd1885ae4cbf191332ae66f8a214e52fb226ba43 in linux-6.6.y/6.6.44
85cf43c554e438e2e12b0fe109688c9533e4d93f in mainline linux
|
|
and add restrict qualifiers. While here, rename the BUGS section
to CAVEATS since they're really "these probably don't do what you
want" notes and not things that need fixing.
ok millert@
|
|
ok kettenis@
|
|
OK jca@
|
|
|
|
|
|
firmware and requires us to shut down an initial "light" firmware that
was presumably loaded bu the system firmware. For now the required
firmwares are not packaged and need to be copied from the Windows
install.
ok patrick@
|
|
|
|
If an interrupt-generating device does not have an interrupt-parent
property, its interrupt parent is assumed to be its devicetree
parent.
Implement this aspect of the spec in the same way as Linux does by not
just looking at the immediate parent but keep on walking up the tree
until we hit a node with an "interrupt-controller" property or a node
that has an "interrupt-parent" property.
ok patrick@
|
|
various Intel SoCs. The driver takes care of calling the AML methods
needed to enter low power idle states during suspend-to-idle (S0i).
The driver also implements some debug code that prints the residency of
various power states in dmesg. Based on some earlier code by jcs@
ok jcs@
|
|
3720.
|
|
that it is emulating them by setting a bright (or bold) flag; however,
when the colour is changed from a bright colour (say SGR 96) to a
non-bright (say SGR 36), the flag is not reset, so the new colour
remains as bright. SGR 39 (default colour) also does not reset, so you
end up with the bright default colour. Work around this by sending SGR 0
when switching away from a bright colour, and disable AX for TERM=linux.
Also make the check for AX simpler and do not check for the op
capability is not actually used. GitHub issue 3976.
|
|
|
|
selection: if selecting the element below the deleted one fails (because
as the last one), select the one above it instead. From Daniel Mueller,
GitHub issue 4043.
|
|
will return NULL if there are no automatic buffers.
|
|
|
|
- radiusd_file(8) is section 8, not 5
|
|
radiusd_eap2mschap(8).
|
