From: syzbot <syzbot+fbd7ba7207767ed15165@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bfoster@redhat.com, darrick.wong@oracle.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, maz@kernel.org, oleg@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: WARNING: ODEBUG bug in exit_to_user_mode_prepare
Date: Thu, 08 Oct 2020 01:44:07 -0700 [thread overview]
Message-ID: <000000000000cb8c0605b124d53c@google.com> (raw)
In-Reply-To: <0000000000006226c805adf16cb8@google.com>
syzbot suspects this issue was fixed by commit:
commit 9c516e0e4554e8f26ab73d46cbc789d7d8db664d
Author: Brian Foster <bfoster@redhat.com>
Date: Tue Aug 18 15:05:58 2020 +0000
xfs: finish dfops on every insert range shift iteration
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=157f71e0500000
start commit: dcc5c6f0 Merge tag 'x86-urgent-2020-08-30' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
dashboard link: https://syzkaller.appspot.com/bug?extid=fbd7ba7207767ed15165
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1447c115900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1344f9fe900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfs: finish dfops on every insert range shift iteration
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2020-10-08 8:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000006226c805adf16cb8@google.com>]
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=000000000000cb8c0605b124d53c@google.com \
--to=syzbot+fbd7ba7207767ed15165@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).