From: Peter Xu <peterx@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+ddf4b4c0005944105a9e@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in try_to_migrate_one (2)
Date: Mon, 15 Apr 2024 11:43:17 -0400 [thread overview]
Message-ID: <Zh1LFYTrAq1JNcXz@x1n> (raw)
In-Reply-To: <20240411125513.b779991117a4dea92ce77269@linux-foundation.org>
On Thu, Apr 11, 2024 at 12:55:13PM -0700, Andrew Morton wrote:
> On Wed, 10 Apr 2024 19:04:21 -0700 syzbot <syzbot+ddf4b4c0005944105a9e@syzkaller.appspotmail.com> wrote:
>
> > syzbot has found a reproducer for the following issue on:
>
> Thanks.
>
> > HEAD commit: 480e035fc4c7 Merge tag 'drm-next-2024-03-13' of https://gi..
> > git tree: upstream
> > console+strace: https://syzkaller.appspot.com/x/log.txt?x=14db82bd180000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=1e5b814e91787669
> > dashboard link: https://syzkaller.appspot.com/bug?extid=ddf4b4c0005944105a9e
> > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13111a4d180000
>
> Seems to be userfaultfd related.
>
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156ae155180000
I can't easily trigger with the reproducer, neither did I get more
information from the syzbot reproducer, and it doesn't include an
UFFDIO_REGISTER.
Before go reading more on syzbot itself on this specific reproducer, I'll
see whether I can come up with something better than commit c2da319c2e2: I
don't remember the details why I didn't do the sanity check when updating
the pgtable rather than walking it. I'll give it a shot this time.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2024-04-15 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 11:25 syzbot
2024-04-11 2:04 ` syzbot
2024-04-11 19:55 ` Andrew Morton
2024-04-15 15:43 ` Peter Xu [this message]
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=Zh1LFYTrAq1JNcXz@x1n \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+ddf4b4c0005944105a9e@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