From: Hillf Danton <hdanton@sina.com>
To: Ubisectech Sirius <bugreport@ubisectech.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org
Subject: Re: INFO: rcu detected stall in nsim_fib_event_work
Date: Sat, 3 Feb 2024 16:16:20 +0800 [thread overview]
Message-ID: <20240203081620.486-1-hdanton@sina.com> (raw)
In-Reply-To: <4db12050-bd87-487c-8298-7ac8e8393d79.bugreport@ubisectech.com>
On Sat, 03 Feb 2024 14:16:16 +0800 Ubisectech Sirius <bugreport@ubisectech.com>
> Hello.
> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
> Recently, our team has discovered a issue in Linux kernel 6.8.0-rc2-g6764c317b6bb.
> Attached to the email were a POC file of the issue.
Could you test if the fix [1] syzbot tested a while before works for you?
[1] https://lore.kernel.org/lkml/000000000000c041c206103c2f22@google.com/
prev parent reply other threads:[~2024-02-03 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 6:16 Ubisectech Sirius
2024-02-03 8:16 ` Hillf Danton [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=20240203081620.486-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=bugreport@ubisectech.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-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
all inboxes | Powered by JetHome®