From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.1
Date: Thu, 27 Oct 2022 15:47:03 +0200 [thread overview]
Message-ID: <Y1qL1zsNFc6w2WTd@infradead.org> (raw)
The following changes since commit 02341a08c9dec5a88527981b0bdf0fb6f7499cbf:
block: fix memory leak for elevator on add_disk failure (2022-10-22 15:14:38 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.1-2022-10-27
for you to fetch changes up to fe8714b04fb137aa62e9a69424c48b5301b721b9:
nvme-multipath: set queue dma alignment to 3 (2022-10-25 08:07:53 -0700)
----------------------------------------------------------------
nvme fixes for Linux 6.1
- make the multipath dma alignment to match the non-multipath one
(Keith Busch)
- fix a bogus use of sg_init_marker() (Nam Cao)
- fix circulr locking in nvme-tcp (Sagi Grimberg)
----------------------------------------------------------------
Keith Busch (1):
nvme-multipath: set queue dma alignment to 3
Nam Cao (1):
nvme-tcp: replace sg_init_marker() with sg_init_table()
Sagi Grimberg (1):
nvme-tcp: fix possible circular locking when deleting a controller under memory pressure
drivers/nvme/host/multipath.c | 1 +
drivers/nvme/host/tcp.c | 13 +++++++++++--
2 files changed, 12 insertions(+), 2 deletions(-)
next reply other threads:[~2022-10-27 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 13:47 Christoph Hellwig [this message]
2022-10-27 13:50 ` [GIT PULL] nvme fixes for Linux 6.1 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-12-07 14:09 Christoph Hellwig
2022-12-07 15:55 ` Jens Axboe
2022-12-02 9:35 Christoph Hellwig
2022-12-02 15:01 ` Jens Axboe
2022-10-20 8:57 Christoph Hellwig
2022-10-20 12:44 ` Jens Axboe
2022-10-12 11:43 Christoph Hellwig
2022-10-12 13:16 ` Jens Axboe
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=Y1qL1zsNFc6w2WTd@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).