From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 5.17
Date: Thu, 3 Feb 2022 12:38:35 -0700 [thread overview]
Message-ID: <26d483ec-e397-822b-343e-3f7e9f09927f@kernel.dk> (raw)
In-Reply-To: <YfwukSSzRWJE2Jy2@infradead.org>
On 2/3/22 12:35 PM, Christoph Hellwig wrote:
> 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.infradead.org/nvme.git tags/nvme-5.17-2022-02-03
>
> for you to fetch changes up to 6a51abdeb259a56d95f13cc67e3a0838bcda0377:
>
> nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts() (2022-02-03 07:30:57 +0100)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 5.17
>
> - fix a use-after-free in rdm and tcp controller reset (Sagi Grimberg)
> - fix the state check in nvmf_ctlr_matches_baseopts (Uday Shankar)
>
> ----------------------------------------------------------------
> 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
>
> Uday Shankar (1):
> nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
>
> drivers/nvme/host/core.c | 9 ++++++++-
> drivers/nvme/host/fabrics.h | 1 +
> drivers/nvme/host/rdma.c | 1 +
> drivers/nvme/host/tcp.c | 1 +
> 4 files changed, 11 insertions(+), 1 deletion(-)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2022-02-03 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 19:35 [GIT PULL] nvme fixes for Linux 5.17 Christoph Hellwig
2022-02-03 19:38 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 7:33 Christoph Hellwig
2022-02-24 14:03 ` Jens Axboe
2022-02-10 7:42 Christoph Hellwig
2022-02-10 13:57 ` Jens Axboe
2022-02-22 17:21 ` Christoph Hellwig
2022-02-22 17:26 ` Jens Axboe
2022-02-22 17:29 ` Christoph Hellwig
2022-01-27 7:19 Christoph Hellwig
2022-01-27 13:53 ` 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=26d483ec-e397-822b-343e-3f7e9f09927f@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--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 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.