[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250328170011.GD29527@redhat.com>
Date: Fri, 28 Mar 2025 18:00:12 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: syzbot <syzbot+62262fdc0e01d99573fc@...kaller.appspotmail.com>
Cc: asmadeus@...ewreck.org, brauner@...nel.org, dhowells@...hat.com,
ericvh@...nel.org, jack@...e.cz, jlayton@...nel.org,
kprateek.nayak@....com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux_oss@...debyte.com,
lucho@...kov.net, mjguzik@...il.com, netfs@...ts.linux.dev,
swapnil.sapkal@....com, syzkaller-bugs@...glegroups.com,
v9fs@...ts.linux.dev, viro@...iv.linux.org.uk
Subject: Re: [syzbot] [netfs?] INFO: task hung in netfs_unbuffered_write_iter
Dear syzbot,
On 03/28, syzbot wrote:
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-by: syzbot+62262fdc0e01d99573fc@...kaller.appspotmail.com
> Tested-by: syzbot+62262fdc0e01d99573fc@...kaller.appspotmail.com
Thanks. so the previous
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
report suggests that upstream/master has another/unrelated issue(s).
As for the patches from me or Prateek (thanks again!), I think that
the maintainers should take a look.
But at this point I am mostly confident that the bisected commit aaec5a95d5961
("pipe_read: don't wake up the writer if the pipe is still full") is innocent,
it just reveals yet another problem.
I guess (I hope ;) Prateek agrees.
Oleg.
Powered by blists - more mailing lists