From: Christian Brauner <brauner@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
syzbot <syzbot+e245f0516ee625aaa412@syzkaller.appspotmail.com>,
djwong@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
llvm@lists.linux.dev, nathan@kernel.org, ndesaulniers@google.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [xfs?] INFO: task hung in __fdget_pos (4)
Date: Mon, 4 Sep 2023 10:11:41 +0200 [thread overview]
Message-ID: <20230904-beleben-adipositas-ac1ed398927d@brauner> (raw)
In-Reply-To: <ZPUSPAnuGLLe3QWH@dread.disaster.area>
On Mon, Sep 04, 2023 at 09:09:48AM +1000, Dave Chinner wrote:
> On Mon, Sep 04, 2023 at 12:47:53AM +0200, Mateusz Guzik wrote:
> > On 9/4/23, Dave Chinner <david@fromorbit.com> wrote:
> > > On Sun, Sep 03, 2023 at 10:33:57AM +0200, Mateusz Guzik wrote:
> > >> On Sun, Sep 03, 2023 at 03:25:28PM +1000, Dave Chinner wrote:
> > >> > On Sat, Sep 02, 2023 at 09:11:34PM -0700, syzbot wrote:
> > >> > > Hello,
> > >> > >
> > >> > > syzbot found the following issue on:
> > >> > >
> > >> > > HEAD commit: b97d64c72259 Merge tag
> > >> > > '6.6-rc-smb3-client-fixes-part1' of..
> > >> > > git tree: upstream
> > >> > > console output:
> > >> > > https://syzkaller.appspot.com/x/log.txt?x=14136d8fa80000
> > >> > > kernel config:
> > >> > > https://syzkaller.appspot.com/x/.config?x=958c1fdc38118172
> > >> > > dashboard link:
> > >> > > https://syzkaller.appspot.com/bug?extid=e245f0516ee625aaa412
> > >> > > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for
> > >> > > Debian) 2.40
> > >> > >
> > >> > > Unfortunately, I don't have any reproducer for this issue yet.
> > >> >
> > >> > Been happening for months, apparently, yet for some reason it now
> > >> > thinks a locking hang in __fdget_pos() is an XFS issue?
> > >> >
> > >> > #syz set subsystems: fs
> > >> >
> > >>
> > >> The report does not have info necessary to figure this out -- no
> > >> backtrace for whichever thread which holds f_pos_lock. I clicked on a
> > >> bunch of other reports and it is the same story.
> > >
> > > That's true, but there's nothing that points at XFS in *any* of the
> > > bug reports. Indeed, log from the most recent report doesn't have
> > > any of the output from the time stuff hung. i.e. the log starts
> > > at kernel time 669.487771 seconds, and the hung task report is at:
> > >
> >
> > I did not mean to imply this is an xfs problem.
> >
> > You wrote reports have been coming in for months so it is pretty clear
> > nobody is investigating.
>
> Which is pretty much the case for all filesystem bug reports from
> syzbot except for those reported against XFS. Almost nobody else is
I'll try to address syzkaller reports that we do get for VFS issues
asap but often they're just not VFS issues or have no reproducer.
next prev parent reply other threads:[~2023-09-04 8:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 4:11 [syzbot] [xfs?] INFO: task hung in __fdget_pos (4) syzbot
2023-09-03 5:25 ` Dave Chinner
2023-09-03 8:33 ` Mateusz Guzik
2023-09-03 18:01 ` Al Viro
2023-09-03 18:57 ` Mateusz Guzik
2023-09-03 19:51 ` Al Viro
2023-09-03 20:04 ` Mateusz Guzik
2023-09-06 17:53 ` Aleksandr Nogikh
2023-09-03 22:27 ` Dave Chinner
2023-09-03 22:47 ` Mateusz Guzik
2023-09-03 23:09 ` Dave Chinner
2023-09-04 8:11 ` Christian Brauner [this message]
2023-09-04 8:23 ` Christian Brauner
2023-09-04 8:55 ` Dave Chinner
2023-09-03 23:13 ` Al Viro
2023-09-04 1:45 ` Dave Chinner
2023-09-04 3:02 ` Al Viro
2023-09-04 3:26 ` Theodore Ts'o
2023-09-04 6:09 ` Mateusz Guzik
2023-11-30 16:58 ` [syzbot] [fs] " syzbot
2024-09-21 5:58 ` syzbot
2024-10-31 13:38 ` 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=20230904-beleben-adipositas-ac1ed398927d@brauner \
--to=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mjguzik@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzbot+e245f0516ee625aaa412@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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).