NishiSearch

Web This site Trusted

25 result(s) for “if com open now site address wilhelm de site can kernel org site does ball so site:cdn.kernel.org” · 870 ms

Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.

Freshness: no result on this page carries a fetch time yet (indexed before the fetch epoch was stored beside the doc)

Found with ksmbdzzer [2], a KSMBD fuzzer that drives libFuzzer with a kcov-dataflow [1] coverage vector: it folds each instrumented comparison/argument's runtime operand value together with its PC (the default arm mixes them as pc⊕val) so that a new operand value at a known site counts as new coverage
from the top result below

commit 500df175a7f9e6bc1a9c328590ca5150f84f9ff0 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.6
The patch does not fix the issue completely, so revert for now and wait for an updated version

commit 81d3924095fd017e473332a9b6dd6dd0e3d9a59b Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.13
The driver does not support modem status notifications and instead used to fetch the modem status once at open() and subsequently operate on and report stale state

commit 8b73de7da85fde281a385e0b26eda9bffd3ca477 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.156
The driver does not support modem status notifications and instead used to fetch the modem status once at open() and subsequently operate on and report stale state

commit 3696cfb7acec262a298e60f9fc0da59d8fc2451e Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.104
org Tested-by: Pavel Machek (CIP) Tested-by: Salvatore Bonaccorso Tested-by: Peter Schneider Tested-by: Florian Fainelli Tested-by: Dominique Martinet Tested-by: Francesco Dolcini Tested-by: Ron Economos Tested-by: Brett A C Sheffield Tested-by: Mark Brown Tested-by: Shuah Khan Tested-by: Harshit Mogalapalli Signed-off

commit bf3be28f6721e24961992ebb9e61c0cf21a56806 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.45
org Tested-by: Pavel Machek (CIP) Tested-by: Peter Schneider Tested-by: Florian Fainelli Tested-by: Ron Economos Tested-by: Brett A C Sheffield Tested-by: Wentao Guan Tested-by: Mark Brown Tested-by: Shuah Khan Tested-by: Shuah Khan Tested-by: Miguel Ojeda Tested-by: Barry K

commit c610b395b0a512dbf32dd0c38897404a7c0011bd Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.152
org Tested-by: Peter Schneider Tested-by: Pavel Machek (CIP) Tested-by: Florian Fainelli Tested-by: Wentao Guan Tested-by: Francesco Dolcini Tested-by: Ron Economos Tested-by: Brett A C Sheffield Tested-by: Mark Brown Tested-by: Shuah Khan Tested-by: Miguel Ojeda Signed-off-by: Greg Kroah-Hartman commit

commit 25c76bea853d0db65b51fb4697a47cbfd9e35e76 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.8
If userspace then renders to what it believes is now the back buffer (but HW is still latched to it

commit ffc82ed665314ccf141abc4710830f3f424d98ea Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.9
org Tested-by: Ronald Warsow Tested-by: Justin M

commit 1efe5d048a391de3ead2804b2e7f86376c356cc5 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.44
org Signed-off-by: Greg Kroah-Hartman Signed-off-by: Greg Kroah-Hartman commit 10be509fa8fd95d1e47d40d1f68b0b26dfe9d572 Author: Oliver Hartkopp Date: Fri Aug 7 09:52:11 2026 +0200 can: isotp: fix timer drain order, wakeup handling and tx_gen ordering commit 050f010f920da17c1044a4f174766ad553e770b6 upstream

commit 833291ee77846538926c990bcb468f6f54e9af50 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.101
Contrary to what was stated on d36349ea73d8 ("Bluetooth: hci_conn: Fix running bis_cleanup for hci_conn->type PA_LINK") the PA_LINK does in fact needs to run bis_cleanup in order to terminate the PA Sync, since that is bond to the listening socket which is the entity that controls the lifetime of PA Sync, so if it is

commit 2609d60e2f6d0b8a96563baa08b56482962cebaa Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.6
This missed the case where background I/O holds the final reference after userspace close() returns, and required explicit maintenance at each close-path site

commit 1f99e9ab748fc5c32120de9c4eca31abfe54a4d5 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.46
arm), so this can cause make oldconfig to loop indefinitely when CONFIG_SMP=n: $ make ARCH=arm allmodconfig $ sed -i "/CONFIG_SMP=y/d

commit d27334b2888c10d2b60c954c59b186182d833107 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.151
org/drm/xe/kernel/-/work_items/8412 Tested-by: Alexander Kaplan Cc: Signed-off-by: Kai Vehmanen Link: https://patch

commit 79643295eba17affbd16ca97f3ef04c90266b28c Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.157
Setting hwc->config should be safe even if there is an error so use this opportunity to simplify the code

commit aa0e49877a2e61e9f4ca10e039727a34f59e9964 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.148
If a vCPU stays scheduled out (or blocked) while the last pCPU it ran on goes through a hotplug cycle (online->offline->online), and the vCPU then resumes execution on the same pCPU, then it is possible for it to run with an ASID that has now been assigned to a different vCPU, resulting in stale TLB translations being

commit 856a9b51680cbbed1ace1207b29e424a616cff48 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.42
If a vCPU stays scheduled out (or blocked) while the last pCPU it ran on goes through a hotplug cycle (online->offline->online), and the vCPU then resumes execution on the same pCPU, then it is possible for it to run with an ASID that has now been assigned to a different vCPU, resulting in stale TLB translations being

commit 2a3da1f4966798b0b48ce302944ad356b2c98b5d Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.265
org Fixes: ef67959c4253 ("hwmon: (adt7470) Convert to use regmap") Signed-off-by: Luiz Angelo Daros de Luca Link: https://lore

commit 78ed1e47aca1a79488df010fd584502de6aef744 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.266
Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via

commit 0eb903b5b519d037c723d47a58c5d4f20eed7342 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.216
org Tested-by: Pavel Machek (CIP) Tested-by: Florian Fainelli Tested-by: Barry K

commit a300e35c0a4b4a38fb53742ea6e2a203c98ee523 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.5
smb2_read_pipe() allocates only the payload size, so the alignment padding can expose up to seven bytes of uninitialized kernel heap memory

commit 7e6e670547210424443261b2d54d2acfff85a37c Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.183
org Tested-by: Peter Schneider Tested-by: Pavel Machek (CIP) Tested-by: Salvatore Bonaccorso Tested-by: Florian Fainelli Tested-by: Francesco Dolcini Tested-by: Ron Economos Tested-by: Brett A C Sheffield Tested-by: Mark Brown Tested-by: Shuah Khan Tested-by: Miguel Ojeda Signed-off-by: Greg Kroah-Hartman commit

commit f6388029ea9e2c9e807d73827658738ea131faee Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.51
smb2_read_pipe() allocates only the payload size, so the alignment padding can expose up to seven bytes of uninitialized kernel heap memory

commit 7cfc41f8e80f11ffa8382ed1a505154ceffb79c7 Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.50
com Fixes: 5d2146a3354f ("selftests/mm: skip mlock tests if nobody user can't read it") Signed-off-by: Injae Ryou Cc: Brendan Jackman Cc: B

commit dc6160265ffc795a1832bc1424f58291d152c7bb Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.153
Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via

commit 05208478041ccec1b348d25e1df5c4013608590e Author: Greg Kroah

https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.184
However, there exists a race window where this check can be bypassed: ring_buffer_lock_reserve cpu_buffer = buffer->buffers[cpu]; // cpu_buffer_a rb_reserve_next_event rb_start_commit // inc committing if (unlikely(READ_ONCE(cpu_buffer->buffer)