All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Pengfei Xu <pengfei.xu@intel.com>,
	lihuafei1@huawei.com, rostedt@goodmis.org,
	linux-kernel@vger.kernel.org, lkp@intel.com,
	quic_neeraju@quicinc.com, paulmck@kernel.org, heng.su@intel.com
Subject: Re: [Syzkaller & bisect] There is "task hung in synchronize_rcu bisect" in v6.3-rc2 kernel
Date: Thu, 13 Apr 2023 15:55:01 +0200	[thread overview]
Message-ID: <ZDgJtWmSmGeY2aJl@localhost.localdomain> (raw)
In-Reply-To: <441aa796-5c39-1cf5-c71a-f04633773968@kernel.dk>

Le Thu, Apr 13, 2023 at 06:40:16AM -0600, Jens Axboe a écrit :
> Is there a reproducer for this one so we can take a look? It's not
> impossible to get into this state if you muck with signals, eg ring
> exit work is queued but needs requests to complete, and the latter
> is prevented by deliberately sending a SIGSTOP to the task that needs
> to complete them.

Yep, the original message provides all the necessary steps to reproduce:

     https://lore.kernel.org/lkml/ZBG4HOCQIlGFFcIn@xpf.sh.intel.com/

I cross my fingers that you'll be able to trigger it...

Thanks.

  reply	other threads:[~2023-04-13 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 12:20 [Syzkaller & bisect] There is "task hung in synchronize_rcu bisect" in v6.3-rc2 kernel Pengfei Xu
2023-04-13  2:45 ` Pengfei Xu
2023-04-13 11:19   ` Frederic Weisbecker
2023-04-13 11:51     ` Zhang, Qiang1
2023-04-13 12:09     ` Pengfei Xu
2023-04-13 12:40     ` Jens Axboe
2023-04-13 13:55       ` Frederic Weisbecker [this message]
     [not found] ` <20230413070042.1479-1-hdanton@sina.com>
2023-04-13  8:03   ` Pengfei Xu
     [not found]   ` <20230413083017.1518-1-hdanton@sina.com>
2023-04-13  9:08     ` Pengfei Xu

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=ZDgJtWmSmGeY2aJl@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=heng.su@intel.com \
    --cc=lihuafei1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=paulmck@kernel.org \
    --cc=pengfei.xu@intel.com \
    --cc=quic_neeraju@quicinc.com \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.