[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221122150355.41805b9013855cf0433b6612@linux-foundation.org>
Date: Tue, 22 Nov 2022 15:03:55 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Mike Kravetz <mike.kravetz@...cle.com>,
David Hildenbrand <david@...hat.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Peter Xu <peterx@...hat.com>,
John Hubbard <jhubbard@...dia.com>,
syzbot+f0b97304ef90f0d0b1dc@...kaller.appspotmail.com
Subject: Re: [PATCH v1] mm/gup: disallow FOLL_FORCE|FOLL_WRITE on hugetlb
mappings
On Tue, 22 Nov 2022 13:59:25 -0400 Jason Gunthorpe <jgg@...dia.com> wrote:
> > >
> > > While that's certainly valid, it's not the common use case with
> > > hugetlb pages.
> >
> > FWIW, I did check with our product teams and they do not knowingly make use
> > of private mappings without write. Of course, that is only a small and
> > limited sample size.
>
> Yeah, if it is only this case I'm comfortable as well
>
So.... I am to slap a cc:stable on this patch and we're all good?
Powered by blists - more mailing lists