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.17-rc3
Date: Fri, 4 Feb 2022 11:28:47 -0700 [thread overview]
Message-ID: <4c26c740-abde-87a1-3cf0-5f97fad85d4e@kernel.dk> (raw)
Hi Linus,
A set of fixes that should go into this release:
- NVMe pull request
- fix a use-after-free in rdm and tcp controller reset
(Sagi Grimberg)
- fix the state check in nvmf_ctlr_matches_baseopts
(Uday Shankar)
- MD nowait null pointer fix (Song)
- blk-integrity seed advance fix (Martin)
- Fix a dio regression in this merge window (Ilya)
Please pull!
The following changes since commit b879f915bc48a18d4f4462729192435bb0f17052:
dm: properly fix redundant bio-based IO accounting (2022-01-28 12:28:15 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/block-5.17-2022-02-04
for you to fetch changes up to b13e0c71856817fca67159b11abac350e41289f5:
block: bio-integrity: Advance seed correctly for larger interval sizes (2022-02-03 21:09:24 -0700)
----------------------------------------------------------------
block-5.17-2022-02-04
----------------------------------------------------------------
Ilya Dryomov (1):
block: fix DIO handling regressions in blkdev_read_iter()
Jens Axboe (2):
Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-5.17
Merge tag 'nvme-5.17-2022-02-03' of git://git.infradead.org/nvme into block-5.17
Martin K. Petersen (1):
block: bio-integrity: Advance seed correctly for larger interval sizes
Sagi Grimberg (3):
nvme: fix a possible use-after-free in controller reset during load
nvme-tcp: fix possible use-after-free in transport error_recovery work
nvme-rdma: fix possible use-after-free in transport error_recovery work
Song Liu (1):
md: fix NULL pointer deref with nowait but no mddev->queue
Uday Shankar (1):
nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
block/bio-integrity.c | 2 +-
block/fops.c | 33 +++++++++++++++++++--------------
drivers/md/md.c | 8 ++++----
drivers/nvme/host/core.c | 9 ++++++++-
drivers/nvme/host/fabrics.h | 1 +
drivers/nvme/host/rdma.c | 1 +
drivers/nvme/host/tcp.c | 1 +
7 files changed, 35 insertions(+), 20 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-02-04 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 18:28 Jens Axboe [this message]
2022-02-04 20:34 ` [GIT PULL] Block fixes for 5.17-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=4c26c740-abde-87a1-3cf0-5f97fad85d4e@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