From: syzbot <syzbot+0da43efa72f88bd3a8af@syzkaller.appspotmail.com>
To: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
pc@manguebit.org, syzkaller-bugs@googlegroups.com,
yun.zhou@windriver.com
Subject: Re: [syzbot] [netfs?] WARNING in netfs_writepages (3)
Date: Mon, 27 Jul 2026 06:03:03 -0700 [thread overview]
Message-ID: <6a675707.073198cf.94f0f.0031.GAE@google.com> (raw)
In-Reply-To: <1098525.1785155757@warthog.procyon.org.uk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0da43efa72f88bd3a8af@syzkaller.appspotmail.com
Tested-by: syzbot+0da43efa72f88bd3a8af@syzkaller.appspotmail.com
Tested on:
commit: 6836db8d netfs: Fix folio_queue ENOMEM in writeback by..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=170d58c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d69870d5e052935f
dashboard link: https://syzkaller.appspot.com/bug?extid=0da43efa72f88bd3a8af
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-07-27 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 21:44 [syzbot] [netfs?] WARNING in netfs_writepages (3) syzbot
2026-07-07 5:34 ` Forwarded: test syzbot
2026-07-24 6:44 ` syzbot
2026-07-24 10:31 ` [syzbot] [netfs?] WARNING in netfs_writepages (3) David Howells
2026-07-24 17:55 ` syzbot
2026-07-27 12:20 ` David Howells
2026-07-27 12:27 ` syzbot
2026-07-27 12:35 ` David Howells
2026-07-27 13:03 ` syzbot [this message]
[not found] <a48f14e1-8bc6-4d64-9a7f-275b18fb3b29@windriver.com>
2026-07-07 6:07 ` syzbot
[not found] <43065e2f-cc23-44b1-82a7-7ed25d2b98d3@windriver.com>
2026-07-24 17:29 ` 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=6a675707.073198cf.94f0f.0031.GAE@google.com \
--to=syzbot+0da43efa72f88bd3a8af@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yun.zhou@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.