From: Greg KH <gregkh@linuxfoundation.org>
To: Wei Chen <harperchen1110@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: general protection fault in put_page
Date: Sun, 7 Aug 2022 15:46:20 +0200 [thread overview]
Message-ID: <Yu/CLORvJj+2leUQ@kroah.com> (raw)
In-Reply-To: <CAO4mrfcuEtSQFj0MEEagWz7bYiYtg9+iCb_j4QstXc9217YZnw@mail.gmail.com>
On Sun, Aug 07, 2022 at 05:50:56PM +0800, Wei Chen wrote:
> Dear Linux Developer,
>
> Recently when using our tool to fuzz kernel, the following crash was triggered:
>
> HEAD commit: 31f4f5b495a6 Linux 5.4-rc7
> git tree: upstream
> compiler: clang 12.0.0
> console output:
> https://drive.google.com/file/d/1rjxlk2_QNsl6CcOwElvUSq5Yhcafb6Il/view?usp=sharing
> Syzlang reproducer:
> https://drive.google.com/file/d/1MFN7c56voPBkd7LzgO0mGZ_oOQNHyK-w/view?usp=sharing
> kernel config: https://drive.google.com/file/d/1sFjtE830MyLBJYZzwZ9sJRsKdf5EzUTV/view?usp=sharing
>
> However, we tried to use syz-prog2c to convert the Syzlang reproducer
> to C format. But the crash wasn't reproduced by the C program. Please
> use syz-execprog to execute the Syzlang reproducer directly on kernel
> to reproduce the bug.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: Wei Chen <harperchen1110@gmail.com>
As you have a reproducer, please feel free to submit a fix for this,
but:
>
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 16421 Comm: syz-executor Not tainted 5.4.0-rc7+ #28
Wow that ia a _VERY_ old and obsolete kernel version. Please try
something more modern, that is not a valid kernel release to be testing
at all.
How does 5.19.0 work for you?
thanks,
greg k-h
prev parent reply other threads:[~2022-08-07 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 9:50 general protection fault in put_page Wei Chen
2022-08-07 13:46 ` Greg KH [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=Yu/CLORvJj+2leUQ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=harperchen1110@gmail.com \
--cc=linux-kernel@vger.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