All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4c81dd8129e47afa014d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] upstream boot error: BUG: unable to handle kernel paging request in corrupted (2)
Date: Tue, 25 Apr 2023 14:34:56 -0700	[thread overview]
Message-ID: <00000000000003688a05fa2fe5fa@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    736b378b29d8 Merge tag 'slab-for-6.4' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1527cb84280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=181497fed2dbaf2
dashboard link: https://syzkaller.appspot.com/bug?extid=4c81dd8129e47afa014d
compiler:       arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4c81dd8129e47afa014d@syzkaller.appspotmail.com

8<--- cut here ---
Unable to handle kernel paging request at virtual address 000c019f when read
[000c019f] *pgd=80000080004003, *pmd=00000000
Internal error: Oops: 206 [#1] PREEMPT SMP ARM
Modules linked in:


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

                 reply	other threads:[~2023-04-25 21:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00000000000003688a05fa2fe5fa@google.com \
    --to=syzbot+4c81dd8129e47afa014d@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 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.