From: Greg KH <gregkh@linuxfoundation.org>
To: liujf628995 <liujf628995@126.com>
Cc: catalin.marinas@arm.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzkaller@googlegroups.com, security@kernel.org,
secalert@redhat.com
Subject: Re: use-after-free in kmemleak_scan？
Date: Thu, 29 Jun 2023 08:56:57 +0200 [thread overview]
Message-ID: <2023062958-twistable-rut-e684@gregkh> (raw)
In-Reply-To: <59a9e693.270f.1890529db99.Coremail.liujf628995@126.com>
On Thu, Jun 29, 2023 at 11:19:36AM +0800, liujf628995 wrote:
> hello,here is a crash from syzkaller,it looks like happened in kmemleak scan.It could not be reproduced by syzkaller because this should not have been caused by syscall fuzz.I don't know what rhe reason for this，please check it.My fuzzed linux kernel is linux-6.2（commit/c9c3395d5e3dcc6daee66c6908354d47bf98cb0c）
If you have a reproducer or a patch, we will be glad to review it,
otherwise just sending syzbot reports like this (especially in html
format which is rejected by the mailing lists), will not go very far as
we have loads of them already.
thanks,
greg k-h
next parent reply other threads:[~2023-06-29 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59a9e693.270f.1890529db99.Coremail.liujf628995@126.com>
2023-06-29 6:56 ` Greg KH [this message]
2023-06-29 9:23 ` liujf628995
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=2023062958-twistable-rut-e684@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liujf628995@126.com \
--cc=secalert@redhat.com \
--cc=security@kernel.org \
--cc=syzkaller@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