From: syzbot <syzbot+7227db0fbac9f348dba0@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfs?] BUG: unable to handle kernel NULL pointer dereference in netfs_unbuffered_write
Date: Fri, 06 Mar 2026 20:19:03 -0800 [thread overview]
Message-ID: <69aba737.050a0220.13f275.003c.GAE@google.com> (raw)
In-Reply-To: <20260307035819.274540-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7227db0fbac9f348dba0@syzkaller.appspotmail.com
Tested-by: syzbot+7227db0fbac9f348dba0@syzkaller.appspotmail.com
Tested on:
commit: 325a118c Merge tag 'pci-v7.0-fixes-3' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12be9552580000
kernel config: https://syzkaller.appspot.com/x/.config?x=976ba5a93c4add9e
dashboard link: https://syzkaller.appspot.com/bug?extid=7227db0fbac9f348dba0
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=179cd8d6580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-03-07 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260307035819.274540-1-kartikey406@gmail.com>
2026-03-07 4:19 ` syzbot [this message]
[not found] <20260307010633.41662-1-kartikey406@gmail.com>
2026-03-07 1:21 ` [syzbot] [netfs?] BUG: unable to handle kernel NULL pointer dereference in netfs_unbuffered_write syzbot
[not found] <20260307004103.33153-1-kartikey406@gmail.com>
2026-03-07 0:55 ` syzbot
[not found] <20260307001235.30412-1-kartikey406@gmail.com>
2026-03-07 0:40 ` syzbot
2026-03-06 6:36 syzbot
2026-03-07 7:27 ` David Howells
2026-03-07 8:00 ` 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=69aba737.050a0220.13f275.003c.GAE@google.com \
--to=syzbot+7227db0fbac9f348dba0@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.