From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: syzbot <syzbot+738cca7d7d9754493513@syzkaller.appspotmail.com>,
clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: INFO: task hung in vfs_setxattr (3)
Date: Tue, 15 Sep 2020 09:57:54 +0200 [thread overview]
Message-ID: <20200915075754.GE1791@twin.jikos.cz> (raw)
In-Reply-To: <c268d760-2230-ec66-01d4-d3cd725ea522@suse.com>
On Tue, Sep 15, 2020 at 10:26:26AM +0300, Nikolay Borisov wrote:
>
>
> On 15.09.20 г. 7:59 ч., syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: 7fe10096 Merge branch 'linus' of git://git.kernel.org/pub/..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=140b0853900000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
> > dashboard link: https://syzkaller.appspot.com/bug?extid=738cca7d7d9754493513
> > compiler: gcc (GCC) 10.1.0-syz 20200507
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108d45a5900000
> >
> > The issue was bisected to:
> >
> > commit 6a3c7f5c87854e948c3c234e5f5e745c7c553722
> > Author: Nikolay Borisov <nborisov@suse.com>
> > Date: Thu May 28 08:05:13 2020 +0000
> >
> > btrfs: don't balance btree inode pages from buffered write path
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14884d21900000
> > final oops: https://syzkaller.appspot.com/x/report.txt?x=16884d21900000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=12884d21900000
>
>
> Unlikely, that patch does change the performance characteristics because
> now we don't balance metadata when doing buffered writes but I don't see
> how it can lead to a hang.
Yeah, this patch once got pointed to by syzbot bisection supposedly
causing bug in a completely unrelated subsystem, but it's more likely
that it's making the bisection unreliable.
https://lore.kernel.org/lkml/20200811065013.GI2026@twin.jikos.cz/
prev parent reply other threads:[~2020-09-15 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 4:59 syzbot
2020-09-15 7:26 ` Nikolay Borisov
2020-09-15 7:57 ` David Sterba [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=20200915075754.GE1791@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=syzbot+738cca7d7d9754493513@syzkaller.appspotmail.com \
--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
all inboxes | Powered by JetHome®