Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Fri, 11 Mar 2022 18:15:00 -0500
- Cc: Anders Roxell <anders.roxell@xxxxxxxxxx>, Masami Hiramatsu <mhiramat@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux-Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, linux-trace-devel@xxxxxxxxxxxxxxx
- In-reply-to: <20220311181328.GA1904@kbox>
- References: <CADYN=9+xY5Vku3Ws5E9S60SM5dCFfeGeRBkmDFbcxX0ZMoFing@mail.gmail.com> <20220311112426.7e3cf434@gandalf.local.home> <20220311171123.GA1675@kbox> <20220311130453.54a4e0b2@gandalf.local.home> <20220311181328.GA1904@kbox>
On Fri, 11 Mar 2022 10:13:28 -0800
Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx> 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
[Index of Archives]
[Linux USB Development]
[Linux USB Development]
[Linux Audio Users]
[Yosemite Hiking]
[Linux Kernel]
[Linux SCSI]