From: syzbot <syzbot+7fc112f7a4a0546731c5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Date: Fri, 07 Nov 2025 02:33:08 -0800 [thread overview]
Message-ID: <690dcae4.a70a0220.22f260.0036.GAE@google.com> (raw)
In-Reply-To: <690d9fd4.a70a0220.22f260.0022.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Author: yun.zhou@windriver.com
#syz dup: BUG: corrupted list in dbUpdatePMap
next prev parent reply other threads:[~2025-11-07 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:29 [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap syzbot
2025-11-07 10:21 ` Forwarded: " syzbot
2025-11-07 10:33 ` syzbot [this message]
2025-11-07 10:42 ` syzbot
2025-11-07 11:15 ` syzbot
2025-11-07 11:31 ` 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=690dcae4.a70a0220.22f260.0036.GAE@google.com \
--to=syzbot+7fc112f7a4a0546731c5@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox