Web This site Trusted
16 result(s) for “okapi bm25 site hotchips pp site does apache org site does redhat com site:cdn.kernel.org” · 933 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)
f), page); At the current call site @new_head still has the tail marker (compound_info bit 0 set, PG_head clear), so on CONFIG_DEBUG_VM kernels this hits: kernel BUG at include/linux/page-flags
from the top result below
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
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.101
KVM falls back to instruction emulation, which fails on FPU/XSave instructions (XRSTOR, STMXCSR) that the emulator does not implement
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.148
KVM falls back to instruction emulation, which fails on FPU/XSave instructions (XRSTOR, STMXCSR) that the emulator does not implement
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
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.42
KVM falls back to instruction emulation, which fails on FPU/XSave instructions (XRSTOR, STMXCSR) that the emulator does not implement
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.9
The removal does not clear asoc->new_transport, leaving it pointing to the removed transport
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.266
This, however, does not apply to the first time begin_cpu_udmabuf() is called on an udmabuf, in which case the implementation previously relied on get_sg_table() to perform the cache synchronisation
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.157
make: Leaving directory '/home/tglozar/dev/linux/tools/testing/selftests/bpf' Fix the problem by renaming the variable used for system bpftool from BPFTOOL to SYSTEM_BPFTOOL, so that the new usage does not conflict with the existing one of BPFTOOL
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.183
The removal does not clear asoc->new_transport, leaving it pointing to the removed transport
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.5
org Tested-by: Ronald Warsow Tested-by: Brett A C Sheffield Tested-by: Florian Fainelli Tested-by: Shuah Khan Tested-by: Miguel Ojeda Tested-by: Takeshi Ogasawara Tested-by: Salvatore Bonaccorso Tested-by: Dileep Malepu Tested-by: Wentao Guan Tested-by: Justin M
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.50
org Tested-by: Brett A C Sheffield Tested-by: Wentao Guan Tested-by: Shuah Khan Tested-by: Miguel Ojeda Link: https://lore
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.51
xas_split_alloc() does not have it and needs to be fixed
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
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.2
An skb entering a frag queue is an IP fragment by definition and cannot legitimately carry GSO state: GRO does not merge fragments and the stack segments before it fragments, so only untrusted sources are affected
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.155
An skb entering a frag queue is an IP fragment by definition and cannot legitimately carry GSO state: GRO does not merge fragments and the stack segments before it fragments, so only untrusted sources are affected
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.153
The x25 timers are armed with mod_timer() and cancelled with timer_delete(), so a pending timer holds no reference on the socket and a cancel does not wait for a callback already running on another CPU