From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: linux-block@vger.kernel.org, Paolo Valente <paolo.valente@linaro.org>
Subject: Re: [PATCH 0/2 v4] block: Fix deadlock when merging requests with BFQ
Date: Thu, 24 Jun 2021 18:44:21 -0600 [thread overview]
Message-ID: <b15405cd-2640-58eb-2a0e-aa1b5d377899@kernel.dk> (raw)
In-Reply-To: <20210623093634.27879-1-jack@suse.cz>
On 6/23/21 3:36 AM, Jan Kara wrote:
> Hello,
>
> This patch series fixes a lockdep complaint and a possible deadlock that
> can happen when blk_mq_sched_try_insert_merge() merges and frees a request.
> Jens, can you please merge the series? It seems to have slipped through last
> time when I posted it. Thanks!
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-06-25 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:36 [PATCH 0/2 v4] block: Fix deadlock when merging requests with BFQ Jan Kara
2021-06-23 9:36 ` [PATCH 1/2] bfq: Remove merged request already in bfq_requests_merged() Jan Kara
2021-06-23 9:36 ` [PATCH 2/2] blk: Fix lock inversion between ioc lock and bfqd lock Jan Kara
2021-06-25 0:44 ` Jens Axboe [this message]
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=b15405cd-2640-58eb-2a0e-aa1b5d377899@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@linaro.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