From: syzbot <syzbot+02e64be5307d72e9c309@syzkaller.appspotmail.com>
To: adrian.ratiu@collabora.com, akpm@linux-foundation.org,
andrii@kernel.org, brauner@kernel.org, david@redhat.com,
eadavis@qq.com, felix.moessbauer@siemens.com,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, lorenzo.stoakes@oracle.com,
mjguzik@gmail.com, superman.xpt@gmail.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk, xu.xin16@zte.com.cn
Subject: Re: [syzbot] [fs?] KASAN: null-ptr-deref Write in do_pagemap_cmd
Date: Wed, 25 Jun 2025 16:23:01 -0700 [thread overview]
Message-ID: <685c84d5.a00a0220.2e5631.01a8.GAE@google.com> (raw)
In-Reply-To: <0000000000001bc4a00612d9a7f4@google.com>
syzbot suspects this issue was fixed by commit:
commit 65c66047259fad1b868d4454bc5af95b46a5f954
Author: Penglei Jiang <superman.xpt@gmail.com>
Date: Fri Apr 4 06:33:57 2025 +0000
proc: fix the issue of proc_mem_open returning NULL
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1604cf0c580000
start commit: 80e54e84911a Linux 6.14-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=77b023e9ae0dbb6a
dashboard link: https://syzkaller.appspot.com/bug?extid=02e64be5307d72e9c309
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101e3b8c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ec67a8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: proc: fix the issue of proc_mem_open returning NULL
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-25 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:11 [syzbot] [fs?] KASAN: null-ptr-deref Write in do_pagemap_cmd syzbot
2024-03-05 0:56 ` Edward Adam Davis
2024-03-05 3:28 ` syzbot
2024-03-05 11:38 ` [PATCH] mm/pagemap: fix null ptr deref " Edward Adam Davis
2025-06-25 23:23 ` syzbot [this message]
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=685c84d5.a00a0220.2e5631.01a8.GAE@google.com \
--to=syzbot+02e64be5307d72e9c309@syzkaller.appspotmail.com \
--cc=adrian.ratiu@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=eadavis@qq.com \
--cc=felix.moessbauer@siemens.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mjguzik@gmail.com \
--cc=superman.xpt@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xu.xin16@zte.com.cn \
/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.