From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.3
Date: Fri, 31 Mar 2023 07:37:06 +0900 [thread overview]
Message-ID: <ZCYPEl0cfKtOlkU8@infradead.org> (raw)
The following changes since commit bb430b69422640891b0b8db762885730579a4145:
loop: LOOP_CONFIGURE: send uevents for partitions (2023-03-27 13:27:06 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.3-2023-03-31
for you to fetch changes up to 88eaba80328b31ef81813a1207b4056efd7006a6:
nvme-tcp: fix a possible UAF when failing to allocate an io queue (2023-03-30 11:24:33 +0900)
----------------------------------------------------------------
nvme fixes for Linux 6.3
- mark Lexar NM760 as IGNORE_DEV_SUBNQN (Juraj Pecigos)
- fix a possible UAF when failing to allocate an TCP io queue
(Sagi Grimberg)
----------------------------------------------------------------
Juraj Pecigos (1):
nvme-pci: mark Lexar NM760 as IGNORE_DEV_SUBNQN
Sagi Grimberg (1):
nvme-tcp: fix a possible UAF when failing to allocate an io queue
drivers/nvme/host/pci.c | 3 ++-
drivers/nvme/host/tcp.c | 46 ++++++++++++++++++++++++++--------------------
2 files changed, 28 insertions(+), 21 deletions(-)
next reply other threads:[~2023-03-30 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 22:37 Christoph Hellwig [this message]
2023-03-30 22:39 ` [GIT PULL] nvme fixes for Linux 6.3 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-03-23 4:07 Christoph Hellwig
2023-03-23 19:02 ` Jens Axboe
2023-03-16 7:58 Christoph Hellwig
2023-03-16 13:02 ` Jens Axboe
2023-02-15 18:17 Christoph Hellwig
2023-02-16 3:25 ` 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=ZCYPEl0cfKtOlkU8@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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