From: syzbot <syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
Date: Tue, 13 May 2025 18:13:03 -0700 [thread overview]
Message-ID: <6823ee1f.a00a0220.104b28.0005.GAE@google.com> (raw)
In-Reply-To: <20250513204140.1987-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
Tested-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
Tested on:
commit: ac57c6b0 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1124f2f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea4635ffd6ad5b4a
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1009ecd4580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-05-14 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250513204140.1987-1-hdanton@sina.com>
2025-05-14 1:13 ` syzbot [this message]
[not found] <CAMj1kXEn_fx6=X4ixhmWST1scUH4kY0SXBt1sXT=-5_ctcKGoA@mail.gmail.com>
2025-05-22 14:50 ` [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context syzbot
[not found] <CAMj1kXEUW2arc4E1z5VkqUm6yi_bPyPwUtvg99PpM4bQLpct5w@mail.gmail.com>
2025-05-22 14:17 ` syzbot
[not found] <20250512103556.1921-1-hdanton@sina.com>
2025-05-12 12:16 ` syzbot
2025-05-11 17:44 syzbot
2025-05-21 17:28 ` Ard Biesheuvel
2025-05-22 12:24 ` Christian Brauner
2025-05-22 13:47 ` Ard Biesheuvel
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=6823ee1f.a00a0220.104b28.0005.GAE@google.com \
--to=syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com \
--cc=hdanton@sina.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