linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Teng Wang <wangteng13@nudt.edu.cn>
Cc: 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 rtc_dev_ioctl
Date: Wed, 13 Sep 2023 09:58:16 +0200	[thread overview]
Message-ID: <20230913-oberwasser-zustrom-e17237b2e154@brauner> (raw)
In-Reply-To: <5b52187e.3b86.18a8d4953cf.Coremail.wangteng13@nudt.edu.cn>

On Wed, Sep 13, 2023 at 02:45:07PM +0800, Teng Wang wrote:
> Dear All,This bug was found in linux Kernel v5.14

Familiarize youself with how to report bugs according to our
documentation. This isn't even minimal effort here.

I'll try this nicely once. Continued dumps of similar low-quality bug
reports will elicit a much stronger response.

           reply	other threads:[~2023-09-13  7:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5b52187e.3b86.18a8d4953cf.Coremail.wangteng13@nudt.edu.cn>]

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=20230913-oberwasser-zustrom-e17237b2e154@brauner \
    --to=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).