From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 5.14-final
Date: Fri, 27 Aug 2021 16:31:42 -0600 [thread overview]
Message-ID: <2d7d0f57-b8f4-cd34-4034-25b9047652fa@kernel.dk> (raw)
Hi Linus,
- Revert the mq-deadline priority handling, it's causing serious
performance regressions. While experimental patches exists to fix this
up, it's too late to do so now. Revert it and re-do it properly for
5.15 instead.
- Fix a NULL vs IS_ERR() regression in this release (Dan)
- Fix a mq-deadline accounting regression in this release (Bart)
- Mark cryptoloop as deprecated. It's broken and dm-crypt fully supports
it, and it's actively intefering with loop. Plan on removal for 5.16.
(Christoph)
Please pull!
The following changes since commit a9ed27a764156929efe714033edb3e9023c5f321:
blk-mq: fix is_flush_rq (2021-08-17 20:17:34 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/block-5.14-2021-08-27
for you to fetch changes up to 222013f9ac30b9cec44301daa8dbd0aae38abffb:
cryptoloop: add a deprecation warning (2021-08-27 10:44:54 -0600)
----------------------------------------------------------------
block-5.14-2021-08-27
----------------------------------------------------------------
Bart Van Assche (1):
mq-deadline: Fix request accounting
Christoph Hellwig (1):
cryptoloop: add a deprecation warning
Dan Carpenter (1):
pd: fix a NULL vs IS_ERR() check
Jens Axboe (1):
Revert "block/mq-deadline: Prioritize high-priority requests"
block/mq-deadline.c | 58 +++++++++++++---------------------------------
drivers/block/Kconfig | 4 ++--
drivers/block/cryptoloop.c | 2 ++
drivers/block/paride/pd.c | 2 +-
4 files changed, 21 insertions(+), 45 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-08-27 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 22:31 Jens Axboe [this message]
2021-08-27 23:27 ` [GIT PULL] Block fixes for 5.14-final pr-tracker-bot
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=2d7d0f57-b8f4-cd34-4034-25b9047652fa@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.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