From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
Yury Norov <yury.norov@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nicholas Piggin <npiggin@gmail.com>,
Ding Tianhong <dingtianhong@huawei.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Alexey Klimov <aklimov@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] vmap(): don't allow invalid pages
Date: Wed, 19 Jan 2022 18:57:34 +0000 [thread overview]
Message-ID: <YehfHsuMzvy//Szi@shell.armlinux.org.uk> (raw)
In-Reply-To: <YehR9BiI92q5DSOu@casper.infradead.org>
On Wed, Jan 19, 2022 at 06:01:24PM +0000, Matthew Wilcox wrote:
> On Wed, Jan 19, 2022 at 05:54:15PM +0000, Russell King (Oracle) wrote:
> > On Wed, Jan 19, 2022 at 04:27:32PM +0000, Matthew Wilcox wrote:
> > > On Wed, Jan 19, 2022 at 01:28:14PM +0000, Robin Murphy wrote:
> > > > > + if (WARN_ON(!pfn_valid(page_to_pfn(page))))
> > > >
> > > > Is it page_to_pfn() guaranteed to work without blowing up if page is invalid
> > > > in the first place? Looking at the CONFIG_SPARSEMEM case I'm not sure that's
> > > > true...
> > >
> > > Even if it does blow up, at least it's blowing up here where someone
> > > can start to debug it, rather than blowing up on first access, where
> > > we no longer have the invlid struct page pointer.
> > >
> > > I don't think we have a 'page_valid' function which will tell us whether
> > > a random pointer is actually a struct page or not.
> >
> > Isn't it supposed to be:
> >
> > if (!pfn_valid(pfn)) {
> > handle invalid pfn;
> > }
> >
> > page = pfn_to_page(pfn);
> >
> > Anything else - even trying to convert an invalid page back to a pfn,
> > could well be unreliable (sparsemem or discontigmem).
>
> This function is passed an array of pages. We have no way of doing
> what you propose.
You can't go from a struct page to "this is valid", it's too late by the
time you call vmap() - that's my fundamental point.
If the translation from a PFN to a struct page can return pointers to
something that isn't a valid struct page, then it can also (with
sparsemem) return a pointer to _another_ struct page that could well
be valid depending on how the struct page arrays are laid out in
memory.
To repeat: once you have a struct page, it's too late to determine if
the struct page is valid.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
Yury Norov <yury.norov@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nicholas Piggin <npiggin@gmail.com>,
Ding Tianhong <dingtianhong@huawei.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Alexey Klimov <aklimov@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] vmap(): don't allow invalid pages
Date: Wed, 19 Jan 2022 18:57:34 +0000 [thread overview]
Message-ID: <YehfHsuMzvy//Szi@shell.armlinux.org.uk> (raw)
In-Reply-To: <YehR9BiI92q5DSOu@casper.infradead.org>
On Wed, Jan 19, 2022 at 06:01:24PM +0000, Matthew Wilcox wrote:
> On Wed, Jan 19, 2022 at 05:54:15PM +0000, Russell King (Oracle) wrote:
> > On Wed, Jan 19, 2022 at 04:27:32PM +0000, Matthew Wilcox wrote:
> > > On Wed, Jan 19, 2022 at 01:28:14PM +0000, Robin Murphy wrote:
> > > > > + if (WARN_ON(!pfn_valid(page_to_pfn(page))))
> > > >
> > > > Is it page_to_pfn() guaranteed to work without blowing up if page is invalid
> > > > in the first place? Looking at the CONFIG_SPARSEMEM case I'm not sure that's
> > > > true...
> > >
> > > Even if it does blow up, at least it's blowing up here where someone
> > > can start to debug it, rather than blowing up on first access, where
> > > we no longer have the invlid struct page pointer.
> > >
> > > I don't think we have a 'page_valid' function which will tell us whether
> > > a random pointer is actually a struct page or not.
> >
> > Isn't it supposed to be:
> >
> > if (!pfn_valid(pfn)) {
> > handle invalid pfn;
> > }
> >
> > page = pfn_to_page(pfn);
> >
> > Anything else - even trying to convert an invalid page back to a pfn,
> > could well be unreliable (sparsemem or discontigmem).
>
> This function is passed an array of pages. We have no way of doing
> what you propose.
You can't go from a struct page to "this is valid", it's too late by the
time you call vmap() - that's my fundamental point.
If the translation from a PFN to a struct page can return pointers to
something that isn't a valid struct page, then it can also (with
sparsemem) return a pointer to _another_ struct page that could well
be valid depending on how the struct page arrays are laid out in
memory.
To repeat: once you have a struct page, it's too late to determine if
the struct page is valid.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-01-19 18:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 23:52 [PATCH] vmap(): don't allow invalid pages Yury Norov
2022-01-18 23:52 ` Yury Norov
2022-01-19 0:51 ` Matthew Wilcox
2022-01-19 0:51 ` Matthew Wilcox
2022-01-19 6:17 ` Anshuman Khandual
2022-01-19 6:17 ` Anshuman Khandual
2022-01-19 17:22 ` Yury Norov
2022-01-19 17:22 ` Yury Norov
2022-01-20 3:37 ` Anshuman Khandual
2022-01-20 3:37 ` Anshuman Khandual
2022-01-20 4:27 ` Matthew Wilcox
2022-01-20 4:27 ` Matthew Wilcox
2022-01-21 2:56 ` Yury Norov
2022-01-21 2:56 ` Yury Norov
2022-01-19 11:16 ` Mark Rutland
2022-01-19 11:16 ` Mark Rutland
2022-01-19 17:00 ` Yury Norov
2022-01-19 17:00 ` Yury Norov
2022-01-19 18:06 ` Mark Rutland
2022-01-19 18:06 ` Mark Rutland
2022-01-19 13:28 ` Robin Murphy
2022-01-19 13:28 ` Robin Murphy
2022-01-19 16:27 ` Matthew Wilcox
2022-01-19 16:27 ` Matthew Wilcox
2022-01-19 17:54 ` Russell King (Oracle)
2022-01-19 17:54 ` Russell King (Oracle)
2022-01-19 18:01 ` Matthew Wilcox
2022-01-19 18:01 ` Matthew Wilcox
2022-01-19 18:57 ` Russell King (Oracle) [this message]
2022-01-19 18:57 ` Russell King (Oracle)
2022-01-19 19:35 ` Matthew Wilcox
2022-01-19 19:35 ` Matthew Wilcox
2022-01-19 22:38 ` Russell King (Oracle)
2022-01-19 22:38 ` Russell King (Oracle)
2022-01-19 18:43 ` Robin Murphy
2022-01-19 18:43 ` Robin Murphy
2022-01-19 19:12 ` Russell King (Oracle)
2022-01-19 19:12 ` Russell King (Oracle)
2022-01-20 12:22 ` Robin Murphy
2022-01-20 12:22 ` Robin Murphy
2022-01-20 13:03 ` Russell King (Oracle)
2022-01-20 13:03 ` Russell King (Oracle)
2022-01-20 16:37 ` Robin Murphy
2022-01-20 16:37 ` Robin Murphy
2022-01-20 16:54 ` Russell King (Oracle)
2022-01-20 16:54 ` Russell King (Oracle)
2022-01-20 19:04 ` Matthew Wilcox
2022-01-20 19:04 ` Matthew Wilcox
2022-01-21 5:26 ` Yury Norov
2022-01-21 5:26 ` Yury Norov
2022-01-26 2:50 ` Matthew Wilcox
2022-01-26 2:50 ` Matthew Wilcox
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=YehfHsuMzvy//Szi@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=aklimov@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dingtianhong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yury.norov@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.