From: syzbot <syzbot+00d13e505ef530a45100@syzkaller.appspotmail.com>
To: ardb@kernel.org, jk@ozlabs.org, linux-efi@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [efi?] [fs?] BUG: unable to handle kernel paging request in efivarfs_pm_notify
Date: Sun, 23 Feb 2025 08:29:02 -0800 [thread overview]
Message-ID: <67bb4cce.050a0220.bbfd1.0032.GAE@google.com> (raw)
In-Reply-To: <CAMj1kXE1WgFkP5RG-VhC_P-gMDtyipW7nvE+i+JBSWXW1bqbhg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+00d13e505ef530a45100@syzkaller.appspotmail.com
Tested-by: syzbot+00d13e505ef530a45100@syzkaller.appspotmail.com
Tested on:
commit: ec7518a8 efivarfs: Defer PM notifier registration unti..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git urgent
console output: https://syzkaller.appspot.com/x/log.txt?x=15dfc7a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3a97cba3fb7e034
dashboard link: https://syzkaller.appspot.com/bug?extid=00d13e505ef530a45100
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-02-23 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 10:53 [syzbot] [efi?] [fs?] BUG: unable to handle kernel paging request in efivarfs_pm_notify syzbot
2025-02-23 15:45 ` Ard Biesheuvel
2025-02-23 15:58 ` syzbot
2025-02-23 15:52 ` Ard Biesheuvel
2025-02-23 16:29 ` 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=67bb4cce.050a0220.bbfd1.0032.GAE@google.com \
--to=syzbot+00d13e505ef530a45100@syzkaller.appspotmail.com \
--cc=ardb@kernel.org \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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.