From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+72aa0161922eba61b50e@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, bp@alien8.de, bp@suse.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luto@kernel.org, mingo@redhat.com, netdev@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
x86@kernel.org
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in copy_from_kernel_nofault
Date: Tue, 21 Nov 2023 18:13:36 +0100 [thread overview]
Message-ID: <87jzqb1133.ffs@tglx> (raw)
In-Reply-To: <000000000000c84343060a850bd0@google.com>
On Sun, Nov 19 2023 at 09:53, syzbot wrote:
> HEAD commit: 1fda5bb66ad8 bpf: Do not allocate percpu memory at init st..
> git tree: bpf
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=12d99420e80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2ae0ccd6bfde5eb0
> dashboard link: https://syzkaller.appspot.com/bug?extid=72aa0161922eba61b50e
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16dff22f680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1027dc70e80000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/3e24d257ce8d/disk-1fda5bb6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/eaa9caffb0e4/vmlinux-1fda5bb6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/16182bbed726/bzImage-1fda5bb6.xz
>
> The issue was bisected to:
>
> commit ca247283781d754216395a41c5e8be8ec79a5f1c
> Author: Andy Lutomirski <luto@kernel.org>
> Date: Wed Feb 10 02:33:45 2021 +0000
>
> x86/fault: Don't run fixups for SMAP violations
Reverting that makes the Ooops go away, but wrongly so.
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=103d92db680000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=123d92db680000
> console output: https://syzkaller.appspot.com/x/log.txt?x=143d92db680000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+72aa0161922eba61b50e@syzkaller.appspotmail.com
> Fixes: ca247283781d ("x86/fault: Don't run fixups for SMAP violations")
>
> BUG: unable to handle page fault for address: ffffffffff600000
This is VSYSCALL_ADDR.
So the real question is why the BPF program tries to copy from the
VSYSCALL page, which is not mapped.
Thanks,
tglx
next prev parent reply other threads:[~2023-11-21 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 17:53 syzbot
2023-11-21 17:13 ` Thomas Gleixner [this message]
2023-12-08 14:11 ` Jann Horn
2023-12-08 21:01 ` Thomas Gleixner
2023-12-21 11:59 ` Hou Tao
2024-02-22 14:29 ` Guilherme G. Piccoli
2024-02-22 16:04 ` Alexei Starovoitov
2024-02-23 1:09 ` Guilherme G. Piccoli
2024-02-23 1:11 ` Alexei Starovoitov
2024-02-25 19:03 ` Guilherme G. Piccoli
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=87jzqb1133.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+72aa0161922eba61b50e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=x86@kernel.org \
/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