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 05:27:02 -0700 [thread overview]
Message-ID: <6a674e96.70955b6c.323240.0042.GAE@google.com> (raw)
In-Reply-To: <1097630.1785154821@warthog.procyon.org.uk>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
error: patch failed: fs/netfs/read_pgpriv2.c:53
error: fs/netfs/read_pgpriv2.c: patch does not apply
error: patch failed: fs/netfs/write_issue.c:749
error: fs/netfs/write_issue.c: patch does not apply
Tested on:
commit: f5098b6b Linux 7.2-rc5
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=48ef5c5c0f192153
dashboard link: https://syzkaller.appspot.com/bug?extid=0da43efa72f88bd3a8af
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=141558c6580000
next prev parent reply other threads:[~2026-07-27 12:27 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 [this message]
2026-07-27 12:35 ` David Howells
2026-07-27 13:03 ` syzbot
[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=6a674e96.70955b6c.323240.0042.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.