From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Teng Wang" <wangteng13@nudt.edu.cn>,
brauner@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: Bug: rcu detected stall in sys_nanosleep
Date: Wed, 13 Sep 2023 14:37:46 +0700 [thread overview]
Message-ID: <ZQFmyp-cK_ensG_u@debian.me> (raw)
In-Reply-To: <13067197.3b9a.18a8d519137.Coremail.wangteng13@nudt.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
On Wed, Sep 13, 2023 at 02:54:07PM +0800, Teng Wang wrote:
> Dear All,
> This bug was found in linux Kernel v6.2.10
>
> Syzkaller hit 'INFO: rcu detected stall in sys_nanosleep' bug.
v6.2.y has been EOLed, please reproduce with current mainline (v6.6-rc1).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-09-13 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 6:54 Bug: rcu detected stall in sys_nanosleep Teng Wang
2023-09-13 7:37 ` Bagas Sanjaya [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=ZQFmyp-cK_ensG_u@debian.me \
--to=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=edumazet@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wangteng13@nudt.edu.cn \
/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).