From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Brian Foster <bfoster@redhat.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: iomap: writeback ioend/bio allocation deadlock risk
Date: Fri, 21 May 2021 16:54:45 +0800 [thread overview]
Message-ID: <YKd1VS5gkzQRn+7x@T590> (raw)
In-Reply-To: <20210521083635.GA15311@lst.de>
On Fri, May 21, 2021 at 10:36:35AM +0200, Christoph Hellwig wrote:
> On Fri, May 21, 2021 at 04:35:03PM +0800, Ming Lei wrote:
> > Just wondering why the ioend isn't submitted out after it becomes full?
>
> block layer plugging? Although failing bio allocations will kick that,
> so that is not a deadlock risk.
These ioends are just added to one list stored on local stack variable(submit_list),
how can block layer plugging observe & submit them out?
Chained bios have been submitted already, but all can't be completed/freed
until the whole ioend is done, that submission won't make forward progress.
Thanks,
Ming
next prev parent reply other threads:[~2021-05-21 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 3:27 iomap: writeback ioend/bio allocation deadlock risk Ming Lei
2021-05-21 7:17 ` Christoph Hellwig
2021-05-21 7:31 ` Ming Lei
2021-05-21 7:35 ` Christoph Hellwig
2021-05-21 8:35 ` Ming Lei
2021-05-21 8:36 ` Christoph Hellwig
2021-05-21 8:54 ` Ming Lei [this message]
2021-05-24 15:32 ` Christoph Hellwig
2021-05-24 23:55 ` Dave Chinner
2021-05-25 4:54 ` Ming Lei
2021-05-25 6:28 ` Ming Lei
2021-05-25 8:21 ` Dave Chinner
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=YKd1VS5gkzQRn+7x@T590 \
--to=ming.lei@redhat.com \
--cc=bfoster@redhat.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox