[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAH8bW9s9ENa7QOExV3rOqn-LAEu1RrQd+ijor9o=jhGxm=6ew@mail.gmail.com>
Date: Tue, 25 Jan 2022 18:29:04 -0800
From: Yury Norov <yury.norov@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Nicholas Piggin <npiggin@...il.com>,
Ding Tianhong <dingtianhong@...wei.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Matthew Wilcox <willy@...radead.org>,
Alexey Klimov <aklimov@...hat.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v2] vmap(): don't allow invalid pages
On Tue, Jan 25, 2022 at 6:25 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 18 Jan 2022 17:21:09 -0800 Yury Norov <yury.norov@...il.com> wrote:
>
> > vmap() takes struct page *pages as one of arguments, and user may provide
> > an invalid pointer which would lead to data abort at address translation
> > later.
>
> Does "user" mean userspace code?
>
> If so, please tell us much more about the means by which userspace can
> trigger this problem.
User means user of vmap() API. The discussion is here:
https://lore.kernel.org/linux-mm/20220118235244.540103-1-yury.norov@gmail.com/
I'll send v3 soon with more details in the patch description.
Powered by blists - more mailing lists