From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+3c74b1f0c372e98efc32@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfs?] KASAN: slab-use-after-free Read in netfs_unbuffered_write
Date: Sun, 31 May 2026 12:37:16 +0800 [thread overview]
Message-ID: <tencent_2AB45DD5997E4FB70DBF25F90D8D9240DD07@qq.com> (raw)
In-Reply-To: <6a19f098.abb04025.19af7b.0003.GAE@google.com>
#syz test
diff --git a/fs/netfs/direct_write.c b/fs/netfs/direct_write.c
index 25f8ceb15fad..8af58e4937c8 100644
--- a/fs/netfs/direct_write.c
+++ b/fs/netfs/direct_write.c
@@ -115,8 +115,11 @@ static int netfs_unbuffered_write(struct netfs_io_request *wreq)
/* Check if (re-)preparation failed. */
if (unlikely(test_bit(NETFS_SREQ_FAILED, &subreq->flags))) {
- netfs_write_subrequest_terminated(subreq, subreq->error);
+ if (!stream->construct)
+ netfs_get_subrequest(subreq, netfs_sreq_trace_get_resubmit);
wreq->error = subreq->error;
+ netfs_write_subrequest_terminated(subreq, subreq->error);
+ ret = wreq->error;
break;
}
next prev parent reply other threads:[~2026-05-31 4:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:01 syzbot
2026-05-30 2:13 ` Forwarded: #syz test syzbot
2026-05-31 3:44 ` [syzbot] [netfs?] KASAN: slab-use-after-free Read in netfs_unbuffered_write Edward Adam Davis
2026-05-31 4:04 ` syzbot
2026-05-31 4:37 ` Edward Adam Davis [this message]
2026-05-31 5:02 ` syzbot
2026-06-24 11:04 ` David Howells
2026-06-24 11:35 ` syzbot
2026-06-25 12:50 ` David Howells
2026-06-25 13:16 ` syzbot
[not found] <67F00FBBAAE8747C+20260530021258.1704818-1-hongao@uniontech.com>
2026-05-30 2:36 ` 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=tencent_2AB45DD5997E4FB70DBF25F90D8D9240DD07@qq.com \
--to=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3c74b1f0c372e98efc32@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®