v9fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+62262fdc0e01d99573fc@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, brauner@kernel.org, dhowells@redhat.com,
	 eadavis@qq.com, ericvh@kernel.org, hdanton@sina.com,
	jack@suse.cz,  jlayton@kernel.org, kprateek.nayak@amd.com,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux_oss@crudebyte.com, lucho@ionkov.net,  mjguzik@gmail.com,
	netfs@lists.linux.dev, oleg@redhat.com, pc@manguebit.org,
	 sfrench@samba.org, swapnil.sapkal@amd.com,
	syzkaller-bugs@googlegroups.com,  v9fs@lists.linux.dev,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [netfs?] INFO: task hung in netfs_unbuffered_write_iter
Date: Sun, 03 Aug 2025 05:09:02 -0700	[thread overview]
Message-ID: <688f515e.050a0220.13f73d.0000.GAE@google.com> (raw)
In-Reply-To: <67dedd2f.050a0220.31a16b.003f.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit da8cf4bd458722d090a788c6e581eeb72695c62f
Author: David Howells <dhowells@redhat.com>
Date:   Tue Jul 1 16:38:36 2025 +0000

    netfs: Fix hang due to missing case in final DIO read result collection

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14cfbcf0580000
start commit:   66701750d556 Merge tag 'io_uring-6.16-20250630' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=e29b8115bf337f53
dashboard link: https://syzkaller.appspot.com/bug?extid=62262fdc0e01d99573fc
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1400348c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17b2048c580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: netfs: Fix hang due to missing case in final DIO read result collection

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

       reply	other threads:[~2025-08-03 12:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <67dedd2f.050a0220.31a16b.003f.GAE@google.com>
2025-08-03 12:09 ` syzbot [this message]
     [not found] <20250323184848.GB14883@redhat.com>
     [not found] ` <67e05e30.050a0220.21942d.0003.GAE@google.com>
     [not found]   ` <20250323194701.GC14883@redhat.com>
     [not found]     ` <CAGudoHHmvU54MU8dsZy422A4+ZzWTVs7LFevP7NpKzwZ1YOqgg@mail.gmail.com>
     [not found]       ` <20250323210251.GD14883@redhat.com>
     [not found]         ` <af0134a7-6f2a-46e1-85aa-c97477bd6ed8@amd.com>
     [not found]           ` <CAGudoHH9w8VO8069iKf_TsAjnfuRSrgiJ2e2D9-NGEDgXW+Lcw@mail.gmail.com>
     [not found]             ` <7e377feb-a78b-4055-88cc-2c20f924bf82@amd.com>
     [not found]               ` <f7585a27-aaef-4334-a1de-5e081f10c901@amd.com>
     [not found]                 ` <ff294b3c-cd24-4aa6-9d03-718ff7087158@amd.com>
2025-03-25 12:15                   ` [syzbot] [netfs?] INFO: task hung in netfs_unbuffered_write_iter Oleg Nesterov
2025-03-25 12:36                     ` Dominique Martinet
2025-03-25 13:04                     ` Oleg Nesterov
2025-03-25 14:49                       ` K Prateek Nayak
2025-03-25 14:58                         ` Dominique Martinet
2025-03-26 12:19                           ` Oleg Nesterov
2025-03-26 12:44                             ` Oleg Nesterov
2025-03-26 13:05                               ` Oleg Nesterov
2025-03-27 17:46                           ` K Prateek Nayak
2025-03-27 21:19                             ` syzbot
2025-03-27 22:18                               ` asmadeus
2025-03-28  4:01                                 ` K Prateek Nayak
2025-03-28  4:43                                   ` syzbot
2025-03-28 13:06                                   ` Oleg Nesterov
2025-03-28 13:07                                     ` syzbot
2025-03-28 13:25                                       ` Oleg Nesterov
2025-03-28 13:49                                         ` syzbot
2025-03-28 14:49                                           ` Oleg Nesterov
2025-03-28 15:22                                             ` syzbot
2025-03-28 17:00                                               ` Oleg Nesterov
2025-03-28 17:56                                                 ` K Prateek Nayak
2025-03-28 18:20                                                   ` Oleg Nesterov
2025-03-29  0:00                                                 ` asmadeus
2025-03-29 14:21                                                   ` Oleg Nesterov
2025-03-29 23:27                                                     ` asmadeus
2025-03-30 10:21                                                       ` Oleg Nesterov

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=688f515e.050a0220.13f73d.0000.GAE@google.com \
    --to=syzbot+62262fdc0e01d99573fc@syzkaller.appspotmail.com \
    --cc=asmadeus@codewreck.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=eadavis@qq.com \
    --cc=ericvh@kernel.org \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=mjguzik@gmail.com \
    --cc=netfs@lists.linux.dev \
    --cc=oleg@redhat.com \
    --cc=pc@manguebit.org \
    --cc=sfrench@samba.org \
    --cc=swapnil.sapkal@amd.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=v9fs@lists.linux.dev \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).