[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220125182550.7c693c76fe6520047c2e4f26@linux-foundation.org>
Date: Tue, 25 Jan 2022 18:25:50 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yury Norov <yury.norov@...il.com>
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, 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.
Powered by blists - more mailing lists