From: Steven Rostedt <rostedt@goodmis.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-trace-devel@vger.kernel.org
Subject: Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
Date: Fri, 11 Mar 2022 18:15:00 -0500 [thread overview]
Message-ID: <20220311181500.0be31225@gandalf.local.home> (raw)
In-Reply-To: <20220311181328.GA1904@kbox>
On Fri, 11 Mar 2022 10:13:28 -0800
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> Is that true as well for the user process that has this mapped? Will the
> user process virtual memory that maps to this ever page it out? I
> believe that was the concern. My understanding is by reserving in
> kernel, even though it won't page out on that side, marks the user side
> entry to not let it page out.
My memory of the purpose of SetPageReserve() is a bit fuzzy, and there's
not much use of it in the kernel. Just a hand full. I'll try to investigate
it some more.
>
> The other thing is that this patch applied to 5.10.X on ARM64 does not
> appear to hit this. Is it some weird interaction with something else or
> was 5.10.X just getting lucky?
Perhaps it's because you allocated the page with kzalloc and not just
getting a page directly?
Again, my knowledge in this area is lacking. I'm looking more into it.
-- Steve
next prev parent reply other threads:[~2022-03-11 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:43 [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509 Anders Roxell
2022-03-11 16:24 ` Steven Rostedt
2022-03-11 17:11 ` Beau Belgrave
2022-03-11 18:04 ` Steven Rostedt
2022-03-11 18:13 ` Beau Belgrave
2022-03-11 23:15 ` Steven Rostedt [this message]
2022-03-11 23:28 ` Beau Belgrave
2022-03-11 23:36 ` Steven Rostedt
2022-03-11 23:47 ` Beau Belgrave
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=20220311181500.0be31225@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=anders.roxell@linaro.org \
--cc=beaub@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).