From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Thomas Gleixner <tglx@linutronix.de>, "x86@kernel.org" <x86@kernel.org>
Cc: jannh@google.com, daniel@iogearbox.net, ast@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
john.fastabend@gmail.com,
Andrew Morton <akpm@linux-foundation.org>,
bpf@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, "luto@kernel.org" <luto@kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in copy_from_kernel_nofault
Date: Thu, 22 Feb 2024 11:29:43 -0300 [thread overview]
Message-ID: <c4c422ac-d017-9944-7d03-76ad416b19a4@igalia.com> (raw)
In-Reply-To: <87r0jwquhv.ffs@tglx>
Hi Thomas et.al,
I've been testing some syzkaller reports and found 2 other bugs that are
fixed by this patch (see other report at [0]).
So, is there anything we could do in order to get it properly submitted
/ merged? Lemme know if I can help in anything, I could submit it myself
if you prefer, keeping you as author and adding the tested tags.
BTW, feel free to add:
Tested-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
Thanks,
Guilherme
[0] One is internal and the other I already mailed in:
https://lore.kernel.org/lkml/66cb411b-557a-6a70-57c9-457c969fec24@igalia.com/
next prev parent reply other threads:[~2024-02-22 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c84343060a850bd0@google.com>
[not found] ` <87jzqb1133.ffs@tglx>
2023-12-08 14:11 ` [syzbot] [mm?] BUG: unable to handle kernel paging request in copy_from_kernel_nofault Jann Horn
2023-12-08 21:01 ` Thomas Gleixner
2023-12-21 11:59 ` Hou Tao
2024-02-22 14:29 ` Guilherme G. Piccoli [this message]
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=c4c422ac-d017-9944-7d03-76ad416b19a4@igalia.com \
--to=gpiccoli@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=john.fastabend@gmail.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=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).