From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+306090cfa3294f0bbfb3@syzkaller.appspotmail.com>
Cc: fweisbec@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] INFO: rcu detected stall in sys_lsetxattr
Date: Wed, 20 Apr 2022 14:27:02 +0200 [thread overview]
Message-ID: <20220420122702.lseed5l3lrssyat2@wittgenstein> (raw)
In-Reply-To: <00000000000080e10e05dd043247@google.com>
On Tue, Apr 19, 2022 at 09:16:20AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 40354149f4d7 Add linux-next specific files for 20220414
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=16ae0bd0f00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a44d62051576f6f5
> dashboard link: https://syzkaller.appspot.com/bug?extid=306090cfa3294f0bbfb3
> 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=164417ccf00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104d63d0f00000
>
> The issue was bisected to:
>
> commit e257039f0fc7da36ac3a522ef9a5cb4ae7852e67
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Tue Mar 1 04:04:20 2022 +0000
>
> mount_setattr(): clean the control flow and calling conventions
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14622210f00000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=16622210f00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=12622210f00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+306090cfa3294f0bbfb3@syzkaller.appspotmail.com
> Fixes: e257039f0fc7 ("mount_setattr(): clean the control flow and calling conventions")
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git fs.mount_setattr.cleanup
next prev parent reply other threads:[~2022-04-20 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 16:16 syzbot
2022-04-20 12:27 ` Christian Brauner [this message]
2022-04-20 13:01 ` syzbot
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=20220420122702.lseed5l3lrssyat2@wittgenstein \
--to=brauner@kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=syzbot+306090cfa3294f0bbfb3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®