From: Greg KH <gregkh@linuxfoundation.org>
To: ffhgfv <xnxc22xnxc22@qq.com>
Cc: stable <stable@vger.kernel.org>, peterz <peterz@infradead.org>,
mingo <mingo@redhat.com>, acme <acme@kernel.org>,
namhyung <namhyung@kernel.org>,
"mark.rutland" <mark.rutland@arm.com>,
"alexander.shishkin" <alexander.shishkin@linux.intel.com>,
jolsa <jolsa@kernel.org>, irogers <irogers@google.com>,
"adrian.hunter" <adrian.hunter@intel.com>,
"kan.liang" <kan.liang@linux.intel.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Potential Linux Crash: WARNING in release_bp_slot in linux6.12.24(longterm maintenance)
Date: Thu, 24 Apr 2025 11:32:00 +0200 [thread overview]
Message-ID: <2025042429-certainly-quarters-f699@gregkh> (raw)
In-Reply-To: <tencent_B50959BC76205E0AE666AE21F7A07D017306@qq.com>
On Thu, Apr 24, 2025 at 03:50:53AM -0400, ffhgfv wrote:
> Hello, I found a potential bug titled " WARNING in release_bp_slot " with modified syzkaller in the Linux6.12.24(longterm maintenance, last updated on April 20, 2025).
> If you fix this issue, please add the following tag to the commit: Reported-by: Jianzhou Zhao <xnxc22xnxc22@qq.com>, xingwei lee <xrivendell7@gmail.com>,Penglei Jiang <superman.xpt@gmail.com>
As you have a reproducer, you are in the best position to create a fix
for this as you can test it. Please do so, such that you can get credit
for resolving the issue.
thanks,
greg k-h
prev parent reply other threads:[~2025-04-24 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 7:50 Potential Linux Crash: WARNING in release_bp_slot in linux6.12.24(longterm maintenance) =?gb18030?B?ZmZoZ2Z2?=
2025-04-24 9:32 ` 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=2025042429-certainly-quarters-f699@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=xnxc22xnxc22@qq.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