From: Luis Chamberlain <mcgrof@kernel.org>
To: "Jürgen Groß" <jgross@suse.com>,
"Marek Maślanka" <mmaslanka@google.com>,
"Adam Williamson" <awilliam@redhat.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
lorenzo.stoakes@oracle.com, akpm@linux-foundation.org,
anton.ivanov@cambridgegreys.com, bp@alien8.de,
brendan.higgins@linux.dev, da.gomez@samsung.com,
danielt@kernel.org, dave.hansen@linux.intel.com,
davidgow@google.com, dianders@chromium.org, hpa@zytor.com,
jason.wessel@windriver.com, jikos@kernel.org,
joe.lawrence@redhat.com, johannes@sipsolutions.net,
jpoimboe@kernel.org, kgdb-bugreport@lists.sourceforge.net,
kirill.shutemov@linux.intel.com, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-modules@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-um@lists.infradead.org,
live-patching@vger.kernel.org, luto@kernel.org,
mark.rutland@arm.com, mbenes@suse.cz, mhiramat@kernel.org,
mingo@redhat.com, peterz@infradead.org, petr.pavlu@suse.com,
pmladek@suse.com, richard@nod.at, rmoar@google.com,
rostedt@goodmis.org, rppt@kernel.org, samitolvanen@google.com,
shuah@kernel.org, song@kernel.org, tglx@linutronix.de,
x86@kernel.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [PATCH 6/8] modules: switch to execmem API for remapping as RW and restoring ROX
Date: Fri, 3 Jan 2025 18:07:22 -0800 [thread overview]
Message-ID: <Z3iX2mNtqSYrvYPT@bombadil.infradead.org> (raw)
In-Reply-To: <9878d90f-faf3-4853-9a79-a21b4f58ab4c@suse.com>
On Fri, Jan 03, 2025 at 07:58:13AM +0100, Jürgen Groß wrote:
> On 03.01.25 03:06, Andrew Cooper wrote:
> > > Hi Mike,
> > >
> > > This commit is making my intel box not boot in mm-unstable :>) I bisected it to
> > > this commit.
> >
> > For what it's worth, we've found the same under Xen too.
> >
> > There's one concrete bug in the series, failing to cope with the absence
> > of superpages (fix in
> > https://lore.kernel.org/xen-devel/6bb03333-74ca-4c2c-85a8-72549b85a5b4@suse.com/
> > but not formally posted yet AFAICT).
>
> Now sent out:
>
> https://lore.kernel.org/lkml/20250103065631.26459-1-jgross@suse.com/T/#u
Thanks,
Marek, Adam, can you try this patch? Although the reply here is for
another future series being worked on the fix is for commit
2e45474ab14f ("execmem: add support for cache of large ROX pages").
Luis
next prev parent reply other threads:[~2025-01-04 2:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 7:28 [PATCH 0/8] x86/module: rework ROX cache to avoid writable copy Mike Rapoport
2024-12-27 7:28 ` [PATCH 1/8] x86/mm/pat: cpa-test: fix length for CPA_ARRAY test Mike Rapoport
2025-01-03 11:19 ` Peter Zijlstra
2024-12-27 7:28 ` [PATCH 2/8] x86/mm/pat: drop duplicate variable in cpa_flush() Mike Rapoport
2024-12-27 7:28 ` [PATCH 3/8] x86/mm/pat: Restore large pages after fragmentation Mike Rapoport
2025-01-10 10:36 ` Kirill A. Shutemov
2025-01-10 19:18 ` Luis Chamberlain
2025-01-12 8:54 ` Mike Rapoport
2025-01-13 8:01 ` Kirill A. Shutemov
2025-01-14 11:01 ` Mike Rapoport
2024-12-27 7:28 ` [PATCH 4/8] execmem: add API for temporal remapping as RW and restoring ROX afterwards Mike Rapoport
2024-12-27 7:28 ` [PATCH 5/8] module: introduce MODULE_STATE_GONE Mike Rapoport
2025-01-08 15:43 ` Daniel Thompson
2024-12-27 7:28 ` [PATCH 6/8] modules: switch to execmem API for remapping as RW and restoring ROX Mike Rapoport
2025-01-02 21:30 ` Lorenzo Stoakes
2025-01-03 2:06 ` Andrew Cooper
2025-01-03 5:57 ` Andrew Morton
2025-01-03 10:57 ` Marek Marczykowski-Górecki
2025-01-03 6:58 ` Jürgen Groß
2025-01-04 2:07 ` Luis Chamberlain [this message]
2025-01-05 12:52 ` Marek Maślanka
2024-12-27 7:28 ` [PATCH 7/8] Revert "x86/module: prepare module loading for ROX allocations of text" Mike Rapoport
2024-12-27 7:28 ` [PATCH 8/8] module: drop unused module_writable_address() Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z3iX2mNtqSYrvYPT@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=awilliam@redhat.com \
--cc=bp@alien8.de \
--cc=brendan.higgins@linux.dev \
--cc=da.gomez@samsung.com \
--cc=danielt@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=davidgow@google.com \
--cc=dianders@chromium.org \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=jgross@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=jpoimboe@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=live-patching@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=marmarek@invisiblethingslab.com \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mmaslanka@google.com \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=richard@nod.at \
--cc=rmoar@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox