From: syzbot <syzbot+d11add3a08fc150ce457@syzkaller.appspotmail.com>
To: brauner@kernel.org, gregkh@linuxfoundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] [kernfs?] INFO: task hung in __generic_file_fsync (5)
Date: Sat, 12 Apr 2025 18:08:05 -0700 [thread overview]
Message-ID: <67fb0e75.050a0220.378c5e.0007.GAE@google.com> (raw)
In-Reply-To: <67777f13.050a0220.11076.0003.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 00dac020ca2a2d82c3e4057a930794cca593ea77
Author: Eric Sandeen <sandeen@redhat.com>
Date: Wed Feb 5 22:30:09 2025 +0000
sysv: convert sysv to use the new mount api
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11b380cc580000
start commit: ab75170520d4 Merge tag 'linux-watchdog-6.13-rc6' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=d11add3a08fc150ce457
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1558f8b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16612edf980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: sysv: convert sysv to use the new mount api
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-04-13 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 6:09 [syzbot] [fs?] INFO: task hung in __generic_file_fsync (5) syzbot
2025-04-13 1:08 ` syzbot [this message]
2025-04-14 10:22 ` [syzbot] [kernfs?] " Christian Brauner
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=67fb0e75.050a0220.378c5e.0007.GAE@google.com \
--to=syzbot+d11add3a08fc150ce457@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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