From: Liam Howlett <liam.howlett@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+502859d610c661e56545@syzkaller.appspotmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] WARNING in mbind_range
Date: Tue, 10 Jan 2023 15:22:01 +0000 [thread overview]
Message-ID: <20230110152154.fpydtasxppz2bx3q@revolver> (raw)
In-Reply-To: <20230109160219.1bda9e780e0fdf7b43cd0210@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [230109 19:02]:
> On Mon, 09 Jan 2023 06:15:39 -0800 syzbot <syzbot+502859d610c661e56545@syzkaller.appspotmail.com> wrote:
>
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit: 543b9b2fe10b Add linux-next specific files for 20230109
> > git tree: linux-next
>
> THanks. Will you be performing a bisection?
No need, I see what I did wrong.
>
> > console+strace: https://syzkaller.appspot.com/x/log.txt?x=12978216480000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=ceb6f70a080e19c3
> > dashboard link: https://syzkaller.appspot.com/bug?extid=502859d610c661e56545
> > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=117fcc02480000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1396d7d6480000
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/22f2428ec2eb/disk-543b9b2f.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/6003c7af47cc/vmlinux-543b9b2f.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/ac9a6ad60347/bzImage-543b9b2f.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+502859d610c661e56545@syzkaller.appspotmail.com
> >
> > ------------[ cut here ]------------
> > WARNING: CPU: 0 PID: 5072 at mm/mempolicy.c:797 mbind_range+0x5d2/0x760 mm/mempolicy.c:797
>
> static int mbind_range(struct mm_struct *mm, unsigned long start,
> unsigned long end, struct mempolicy *new_pol)
> {
> VMA_ITERATOR(vmi, mm, start);
> struct vm_area_struct *prev;
> struct vm_area_struct *vma;
> int err = 0;
> pgoff_t pgoff;
>
> prev = vma_prev(&vmi);
> vma = vma_find(&vmi, end);
> if (WARN_ON(!vma))
> return 0;
>
> Liam recently altered this code with "mempolicy: convert to vma iterator"?
Yes, thanks. This helped a lot in seeing what I did here.
...
Thanks,
Liam
prev parent reply other threads:[~2023-01-10 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 6:58 syzbot
2023-01-09 14:15 ` syzbot
2023-01-10 0:02 ` Andrew Morton
2023-01-10 15:22 ` Liam Howlett [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=20230110152154.fpydtasxppz2bx3q@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+502859d610c661e56545@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