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 followup fixes for 5.16-rc3
Date: Sat, 27 Nov 2021 09:04:29 -0700 [thread overview]
Message-ID: <def53d9f-f655-3435-6804-be4482816eed@kernel.dk> (raw)
Hi Linus,
Turns out that the flushing out of pending fixes before the Thanksgiving
break didn't quite work out in terms of timing, so here's a followup
pull request.
- rq_qos_done() should be called regardless of whether or not we're the
final put of the request, it's not related to the freeing of the
state. This fixes an IO stall with wbt that a few users have reported,
a regression in this release.
- Only define zram_wb_devops if it's used, fixing a compilation warning
for some compilers.
Please pull!
The following changes since commit e30028ace8459ea096b093fc204f0d5e8fc3b6ae:
block: fix parameter not described warning (2021-11-25 09:32:19 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/block-5.16-2021-11-27
for you to fetch changes up to d422f40163087408b56290156ba233fc5ada53e4:
zram: only make zram_wb_devops for CONFIG_ZRAM_WRITEBACK (2021-11-26 09:57:32 -0700)
----------------------------------------------------------------
block-5.16-2021-11-27
----------------------------------------------------------------
Jens Axboe (2):
block: call rq_qos_done() before ref check in batch completions
zram: only make zram_wb_devops for CONFIG_ZRAM_WRITEBACK
block/blk-mq.c | 3 ++-
drivers/block/zram/zram_drv.c | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
--
Jens Axboe
next reply other threads:[~2021-11-27 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 16:04 Jens Axboe [this message]
2021-11-27 19:47 ` [GIT PULL] Block followup fixes for 5.16-rc3 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=def53d9f-f655-3435-6804-be4482816eed@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 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.