From: Christoph Hellwig <hch@lst.de>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
jack@suse.cz, axboe@kernel.dk,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
dm-devel@redhat.com, sachinp <sachinp@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>,
dougmill@us.ibm.com
Subject: Re: [next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target
Date: Wed, 29 Sep 2021 08:52:02 +0200 [thread overview]
Message-ID: <20210929065202.GA31534@lst.de> (raw)
In-Reply-To: <86f8e47b-84ca-4cc3-5d5b-f5f11c1d4d1a@linux.vnet.ibm.com>
On Tue, Sep 28, 2021 at 03:53:47PM +0530, Abdul Haleem wrote:
>
> On 9/1/21 7:06 PM, Christoph Hellwig wrote:
>> On Wed, Sep 01, 2021 at 04:47:26PM +0530, Abdul Haleem wrote:
>>> Greeting's
>>>
>>> multiple task hung while adding the vfc disk back to the multipath on my
>>> powerpc box running linux-next kernel
>> Can you retry to reproduce this with lockdep enabled to see if there
>> is anything interesting holding this lock?
>
> LOCKDEP was earlier enabled by default
>
> # cat .config | grep LOCKDEP
> CONFIG_LOCKDEP_SUPPORT=y
>
> BTW, Recreated again on 5.15.0-rc2 mainline kernel and attaching the logs
It seems the reinstate is blocking on the close which is blocking on
flushing dirty data. In other words it looks like the link blocking
looks like the symptom and not the cause.
WARNING: multiple messages have this Message-ID
From: Christoph Hellwig <hch@lst.de>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: axboe@kernel.dk, sachinp <sachinp@linux.vnet.ibm.com>,
jack@suse.cz, linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dm-devel@redhat.com, linux-next <linux-next@vger.kernel.org>,
dougmill@us.ibm.com, Brian King <brking@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target
Date: Wed, 29 Sep 2021 08:52:02 +0200 [thread overview]
Message-ID: <20210929065202.GA31534@lst.de> (raw)
In-Reply-To: <86f8e47b-84ca-4cc3-5d5b-f5f11c1d4d1a@linux.vnet.ibm.com>
On Tue, Sep 28, 2021 at 03:53:47PM +0530, Abdul Haleem wrote:
>
> On 9/1/21 7:06 PM, Christoph Hellwig wrote:
>> On Wed, Sep 01, 2021 at 04:47:26PM +0530, Abdul Haleem wrote:
>>> Greeting's
>>>
>>> multiple task hung while adding the vfc disk back to the multipath on my
>>> powerpc box running linux-next kernel
>> Can you retry to reproduce this with lockdep enabled to see if there
>> is anything interesting holding this lock?
>
> LOCKDEP was earlier enabled by default
>
> # cat .config | grep LOCKDEP
> CONFIG_LOCKDEP_SUPPORT=y
>
> BTW, Recreated again on 5.15.0-rc2 mainline kernel and attaching the logs
It seems the reinstate is blocking on the close which is blocking on
flushing dirty data. In other words it looks like the link blocking
looks like the symptom and not the cause.
WARNING: multiple messages have this Message-ID
From: Christoph Hellwig <hch@lst.de>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: axboe@kernel.dk, sachinp <sachinp@linux.vnet.ibm.com>,
jack@suse.cz, linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dm-devel@redhat.com, linux-next <linux-next@vger.kernel.org>,
dougmill@us.ibm.com, Brian King <brking@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] [next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target
Date: Wed, 29 Sep 2021 08:52:02 +0200 [thread overview]
Message-ID: <20210929065202.GA31534@lst.de> (raw)
In-Reply-To: <86f8e47b-84ca-4cc3-5d5b-f5f11c1d4d1a@linux.vnet.ibm.com>
On Tue, Sep 28, 2021 at 03:53:47PM +0530, Abdul Haleem wrote:
>
> On 9/1/21 7:06 PM, Christoph Hellwig wrote:
>> On Wed, Sep 01, 2021 at 04:47:26PM +0530, Abdul Haleem wrote:
>>> Greeting's
>>>
>>> multiple task hung while adding the vfc disk back to the multipath on my
>>> powerpc box running linux-next kernel
>> Can you retry to reproduce this with lockdep enabled to see if there
>> is anything interesting holding this lock?
>
> LOCKDEP was earlier enabled by default
>
> # cat .config | grep LOCKDEP
> CONFIG_LOCKDEP_SUPPORT=y
>
> BTW, Recreated again on 5.15.0-rc2 mainline kernel and attaching the logs
It seems the reinstate is blocking on the close which is blocking on
flushing dirty data. In other words it looks like the link blocking
looks like the symptom and not the cause.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-09-29 6:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 11:17 [next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target Abdul Haleem
2021-09-01 11:17 ` [dm-devel] " Abdul Haleem
2021-09-01 11:17 ` Abdul Haleem
2021-09-01 13:36 ` Christoph Hellwig
2021-09-01 13:36 ` [dm-devel] " Christoph Hellwig
2021-09-01 13:36 ` Christoph Hellwig
2021-09-28 10:23 ` Abdul Haleem
2021-09-28 10:23 ` [dm-devel] " Abdul Haleem
2021-09-28 10:23 ` Abdul Haleem
2021-09-29 6:52 ` Christoph Hellwig [this message]
2021-09-29 6:52 ` [dm-devel] " Christoph Hellwig
2021-09-29 6:52 ` 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=20210929065202.GA31534@lst.de \
--to=hch@lst.de \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=brking@linux.vnet.ibm.com \
--cc=dm-devel@redhat.com \
--cc=dougmill@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.com \
/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.