Re: [PATCH v2 1/1] mm: fix folio_pte_batch() on XEN PV

2025-05-03 Thread David Hildenbrand
On 04.05.25 03:28, Andrew Morton wrote: On Fri, 2 May 2025 23:50:19 +0200 Petr Vaněk wrote: On XEN PV, folio_pte_batch() can incorrectly batch beyond the end of a folio due to a corner case in pte_advance_pfn(). Specifically, when the PFN following the folio maps to an invalidated MFN,

Re: [PATCH v2 1/1] mm: fix folio_pte_batch() on XEN PV

2025-05-03 Thread Andrew Morton
On Fri, 2 May 2025 23:50:19 +0200 Petr Vaněk wrote: > On XEN PV, folio_pte_batch() can incorrectly batch beyond the end of a > folio due to a corner case in pte_advance_pfn(). Specifically, when the > PFN following the folio maps to an invalidated MFN, > > expected_pte = pte_advance_pfn(e

Re: [PATCH RFC v3 0/8] kernel-hacking: introduce CONFIG_NO_AUTO_INLINE

2025-05-03 Thread Bart Van Assche
On 5/1/25 8:22 AM, Brendan Jackman wrote: Personally I sometimes spam a bunch of `noinline` into code I'm debugging so this seems like a way to just slap that same thing on the whole tree without dirtying the code, right? If this is for test builds only, has it been consider to add -fno-inline-

Re: NULL pointer dereference in xenbus_thread->...

2025-05-03 Thread Jason Andryuk
On Wed, Apr 30, 2025 at 11:44 AM Jürgen Groß wrote: > I have looked at this issue multiple times now. > > Just some remarks what IMO could go wrong (I didn't find any proof that > this really happened, though), in case someone wants to double check: > > The most probably candidate for something go

Re: NULL pointer dereference in xenbus_thread->...

2025-05-03 Thread Jason Andryuk
On Thu, May 1, 2025 at 8:01 PM Marek Marczykowski-Górecki wrote: > > I'm curious what process_msg+0x18e/0x2f0 is. process_writes() has a > > direct call to wake_up(), but process_msg() calling req->cb(req) may > > be xs_wake_up() which is a thin wrapper over wake_up(). > > So, it's req->cb(req).

Request for patch to fix boot loop issue in Xen 4.17.6

2025-05-03 Thread Ngamia Djabiri Julie
Dear Xen developers, I would like to ask if the following fix can also be included in Xen 4.17.6 (and eventually in the Xen versions after 4.17.6 that don't have the fix) : https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=dd05d265b8abda4cc7206b29cd71b77fb46658bf This bug causes a boot l

[PATCH] xenbus: Allow PVH dom0 a non-local xenstore

2025-05-03 Thread Jason Andryuk
Make xenbus_init() allow a non-local xenstore for a PVH dom0 - it is currently forced to XS_LOCAL. With Hyperlaunch booting dom0 and a xenstore stubdom, dom0 can be handled as a regular XS_HVM following the late init path. Drop the use of xen_initial_domain() and just check for the event channel