All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zqiang <qiang.zhang1211@gmail.com>
Cc: Hao Sun <sunhao.th@gmail.com>, Hillf Danton <hdanton@sina.com>,
	hch@infradead.org, willy@infradead.org,
	Linux MM <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in __init_work
Date: Mon, 18 Oct 2021 06:47:45 +0200	[thread overview]
Message-ID: <20211018044745.GA23657@lst.de> (raw)
In-Reply-To: <d242861c-5c41-0d1b-3f71-43f50e5a3b68@gmail.com>



On Mon, Oct 18, 2021 at 12:43:38PM +0800, Zqiang wrote:
> This is the details of the test, Hope it helps you

Call me stupid, but I can only find the trace and linked to unreadable
google sites that wan't me to log in somehow and no actual details.

If you have a direct link to the reproducer (an attachment would do
it as well) I'd love to try it myself.

Otherwise this commit in the block-5.15 tree should help to catch what
I suspect is the root cause (final ref drop before unregister) earlier
and with a better backtrace:

https://git.kernel.dk/cgit/linux-block/commit/?h=block-5.15&id=a20417611b98e12a724e5c828c472ea16990b71f

  reply	other threads:[~2021-10-18  4:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  1:22 WARNING in __init_work Hao Sun
2021-09-07  7:44 ` Hillf Danton
2021-10-14  2:38   ` Hao Sun
2021-10-18  4:43     ` Zqiang
2021-10-18  4:47       ` Christoph Hellwig [this message]
2021-10-18  7:21         ` Zqiang
2021-10-18  8:15           ` Christoph Hellwig

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=20211018044745.GA23657@lst.de \
    --to=hch@lst.de \
    --cc=hch@infradead.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=sunhao.th@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=willy@infradead.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.