lkml.org 
[lkml]   [2018]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions
On Wed 10-10-18 16:45:41, Andrew Morton wrote:
> On Tue, 9 Oct 2018 17:42:09 -0700 John Hubbard <jhubbard@nvidia.com> wrote:
>
> > > Also, maintainability. What happens if someone now uses put_page() by
> > > mistake? Kernel fails in some mysterious fashion? How can we prevent
> > > this from occurring as code evolves? Is there a cheap way of detecting
> > > this bug at runtime?
> > >
> >
> > It might be possible to do a few run-time checks, such as "does page that came
> > back to put_user_page() have the correct flags?", but it's harder (without
> > having a dedicated page flag) to detect the other direction: "did someone page
> > in a get_user_pages page, to put_page?"
> >
> > As Jan said in his reply, converting get_user_pages (and put_user_page) to
> > work with a new data type that wraps struct pages, would solve it, but that's
> > an awfully large change. Still...given how much of a mess this can turn into
> > if it's wrong, I wonder if it's worth it--maybe?
>
> This is a real worry. If someone uses a mistaken put_page() then how
> will that bug manifest at runtime? Under what set of circumstances
> will the kernel trigger the bug?

At runtime such bug will manifest as a page that can never be evicted from
memory. We could warn in put_page() if page reference count drops below
bare minimum for given user pin count which would be able to catch some
issues but it won't be 100% reliable. So at this point I'm more leaning
towards making get_user_pages() return a different type than just
struct page * to make it much harder for refcount to go wrong...

Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR

\
 
 \ /
  Last update: 2018-10-11 10:50    [W:0.103 / U:6.860 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site