[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR11MB349565A7C67907DE0AF3BDF6F76A9@BYAPR11MB3495.namprd11.prod.outlook.com>
Date: Wed, 17 Aug 2022 05:47:08 +0000
From: "Wang, Haiyue" <haiyue.wang@...el.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"david@...hat.com" <david@...hat.com>,
"apopple@...dia.com" <apopple@...dia.com>,
"linmiaohe@...wei.com" <linmiaohe@...wei.com>,
"Huang, Ying" <ying.huang@...el.com>,
"songmuchun@...edance.com" <songmuchun@...edance.com>,
"naoya.horiguchi@...ux.dev" <naoya.horiguchi@...ux.dev>,
"alex.sierra@....com" <alex.sierra@....com>,
Heiko Carstens <hca@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: RE: [PATCH v6 1/2] mm: migration: fix the FOLL_GET failure on
following huge page
> -----Original Message-----
> From: Andrew Morton <akpm@...ux-foundation.org>
> Sent: Wednesday, August 17, 2022 13:43
> To: Wang, Haiyue <haiyue.wang@...el.com>
> Cc: linux-mm@...ck.org; linux-kernel@...r.kernel.org; david@...hat.com; apopple@...dia.com;
> linmiaohe@...wei.com; Huang, Ying <ying.huang@...el.com>; songmuchun@...edance.com;
> naoya.horiguchi@...ux.dev; alex.sierra@....com; Heiko Carstens <hca@...ux.ibm.com>; Vasily Gorbik
> <gor@...ux.ibm.com>; Alexander Gordeev <agordeev@...ux.ibm.com>; Christian Borntraeger
> <borntraeger@...ux.ibm.com>; Sven Schnelle <svens@...ux.ibm.com>; Mike Kravetz
> <mike.kravetz@...cle.com>
> Subject: Re: [PATCH v6 1/2] mm: migration: fix the FOLL_GET failure on following huge page
>
> On Wed, 17 Aug 2022 03:31:37 +0000 "Wang, Haiyue" <haiyue.wang@...el.com> wrote:
>
> > > > }
> > >
> > > I would be better to fix this for real at those three client code sites?
> >
> > Then 5.19 will break for a while to wait for the final BIG patch ?
>
> If that's the proposal then your [1/2] should have had a cc:stable and
> changelog words describing the plan for 6.0.
>
> But before we do that I'd like to see at least a prototype of the final
> fixes to s390 and hugetlb, so we can assess those as preferable for
Got it, make sense. ;-)
> backporting. I don't think they'll be terribly intrusive or risky?
Powered by blists - more mailing lists