From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+681bbbb80445ead3c040@syzkaller.appspotmail.com>,
hughd@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
Alistair Popple <apopple@nvidia.com>,
David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [syzbot] general protection fault in vma_is_shmem
Date: Sun, 21 Aug 2022 17:10:06 -0700 [thread overview]
Message-ID: <761793f4-cd16-fcc1-8777-f7e032604e1e@nvidia.com> (raw)
In-Reply-To: <20220821163120.df7d936c9f47b6dc875ab763@linux-foundation.org>
On 8/21/22 16:31, Andrew Morton wrote:
> On Sun, 21 Aug 2022 16:18:48 -0700 John Hubbard <jhubbard@nvidia.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
next prev parent reply other threads:[~2022-08-22 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 6:14 syzbot
[not found] ` <20220821013246.a706fa7c2d8cb494efdba02e@linux-foundation.org>
2022-08-21 23:18 ` John Hubbard
2022-08-21 23:31 ` Andrew Morton
2022-08-22 0:10 ` John Hubbard [this message]
2022-08-31 9:40 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=761793f4-cd16-fcc1-8777-f7e032604e1e@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+681bbbb80445ead3c040@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox