From: Oleg Nesterov <oleg@redhat.com>
To: syzbot <syzbot+3815dce0acab6c55984e@syzkaller.appspotmail.com>
Cc: brauner@kernel.org, dhowells@redhat.com, jack@suse.cz,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
pc@manguebit.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [netfs?] INFO: task hung in vfs_utimes (3)
Date: Fri, 19 Sep 2025 09:14:54 +0200 [thread overview]
Message-ID: <20250919071454.GA20615@redhat.com> (raw)
In-Reply-To: <68cca807.050a0220.28a605.0013.GAE@google.com>
On 09/18, syzbot wrote:
>
> syzbot has bisected this issue to:
>
> commit aaec5a95d59615523db03dd53c2052f0a87beea7
> Author: Oleg Nesterov <oleg@redhat.com>
> Date: Thu Jan 2 14:07:15 2025 +0000
>
> pipe_read: don't wake up the writer if the pipe is still full
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175fa534580000
> start commit: 46a51f4f5eda Merge tag 'for-v6.17-rc' of git://git.kernel...
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=14dfa534580000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10dfa534580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8f01d8629880e620
> dashboard link: https://syzkaller.appspot.com/bug?extid=3815dce0acab6c55984e
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17692f62580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1361f47c580000
>
> Reported-by: syzbot+3815dce0acab6c55984e@syzkaller.appspotmail.com
> Fixes: aaec5a95d596 ("pipe_read: don't wake up the writer if the pipe is still full")
#syz dup: [syzbot] [fs?] [mm?] INFO: task hung in v9fs_file_fsync
https://lore.kernel.org/all/68a2de8f.050a0220.e29e5.0097.GAE@google.com/
next prev parent reply other threads:[~2025-09-19 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 22:54 [syzbot] [netfs?] INFO: task hung in vfs_utimes (3) syzbot
2025-09-19 0:47 ` syzbot
2025-09-19 7:14 ` Oleg Nesterov [this message]
2025-09-19 6:48 ` Oleg Nesterov
2025-09-19 12:22 ` Hillf Danton
2025-09-19 13:25 ` Dominique Martinet
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=20250919071454.GA20615@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=syzbot+3815dce0acab6c55984e@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;
as well as URLs for NNTP newsgroup(s).