[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <761793f4-cd16-fcc1-8777-f7e032604e1e@nvidia.com>
Date: Sun, 21 Aug 2022 17:10:06 -0700
From: John Hubbard <jhubbard@...dia.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: syzbot <syzbot+681bbbb80445ead3c040@...kaller.appspotmail.com>,
hughd@...gle.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
syzkaller-bugs@...glegroups.com,
Alistair Popple <apopple@...dia.com>,
David Hildenbrand <david@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>
Subject: Re: [syzbot] general protection fault in vma_is_shmem
On 8/21/22 16:31, Andrew Morton wrote:
> On Sun, 21 Aug 2022 16:18:48 -0700 John Hubbard <jhubbard@...dia.com> wrote:
>
>>> vmas[] array. We haven't messed with gup.c much this time around -
>>> just one patch from Alistair ("mm/gup.c: simplify and fix
>>> check_and_migrate_movable_pages() return codes"). It does touch this
>>> area, but I can't immediately see how it could newly cause this.
>>>
>>
>> Neither can I, even after looking at both of these recent commits to
>> gup.c in this branch:
>>
>> commit 4d1225cd5560 ("mm/gup.c: simplify and fix
>> check_and_migrate_movable_pages() return codes")
>>
>> commit 0e5d6dac6b65 ("mm/gup: fix FOLL_FORCE COW security issue and
>> remove FOLL_COW")
>>
>> As you say, a bisection would really help here.
>
> Might
> https://lkml.kernel.org/r/20220821183547.950370-1-syoshida@redhat.com
> save us?
>
>
aha yes, that looks right.
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists