All of lore.kernel.org
 help / color / mirror / Atom feed
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.2
Date: Thu, 29 Dec 2022 06:41:37 -1000	[thread overview]
Message-ID: <Y63DQSUSW4aQlVJ+@infradead.org> (raw)

The following changes since commit 88d356ca41ba1c3effc2d4208dfbd4392f58cd6d:

  nvme-pci: update sqsize when adjusting the queue depth (2022-12-26 12:10:51 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.2-2022-12-29

for you to fetch changes up to 76807fcd73b818eb9f245ef1035aed34ecdd9813:

  nvme-auth: fix smatch warning complaints (2022-12-28 06:26:35 -1000)

----------------------------------------------------------------
nvme fixes for Linux 6.2

 - fix various problems in handling the Command Supported and Effects log
   (Christoph Hellwig)
 - don't allow unprivileged passthrough of commands that don't transfer
   data but modify logical block content (Christoph Hellwig)
 - add a features and quirks policy document (Christoph Hellwig)
 - fix some really nasty code that was correct but made smatch complain
   (Sagi Grimberg)

----------------------------------------------------------------
Christoph Hellwig (7):
      docs, nvme: add a feature and quirk policy document
      nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition
      nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it
      nvmet: set the LBCC bit for commands that modify data
      nvmet: don't defer passthrough commands with trivial effects to the workqueue
      nvme: also return I/O command effects from nvme_command_effects
      nvme: consult the CSE log page for unprivileged passthrough

Sagi Grimberg (1):
      nvme-auth: fix smatch warning complaints

 .../maintainer/maintainer-entry-profile.rst        |  1 +
 Documentation/nvme/feature-and-quirk-policy.rst    | 77 ++++++++++++++++++++++
 MAINTAINERS                                        |  1 +
 drivers/nvme/host/auth.c                           |  2 +-
 drivers/nvme/host/core.c                           | 32 +++++++--
 drivers/nvme/host/ioctl.c                          | 28 ++++++--
 drivers/nvme/target/admin-cmd.c                    | 37 ++++++-----
 drivers/nvme/target/passthru.c                     | 11 ++--
 include/linux/nvme.h                               |  4 +-
 9 files changed, 159 insertions(+), 34 deletions(-)
 create mode 100644 Documentation/nvme/feature-and-quirk-policy.rst

             reply	other threads:[~2022-12-29 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 16:41 Christoph Hellwig [this message]
2022-12-29 18:32 ` [GIT PULL] nvme fixes for Linux 6.2 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2023-02-15 18:14 Christoph Hellwig
2023-02-16  3:25 ` Jens Axboe
2023-02-09  5:10 Christoph Hellwig
2023-02-09 15:12 ` Jens Axboe
2023-02-02 15:23 Christoph Hellwig
2023-02-02 18:02 ` Jens Axboe
2023-01-26 17:38 Christoph Hellwig
2023-01-26 18:44 ` Jens Axboe
2023-01-20  5:52 Christoph Hellwig
2023-01-20 15:09 ` Jens Axboe
2023-01-12  8:25 Christoph Hellwig
2023-01-12 17:37 ` Jens Axboe
2022-12-22 15:43 Christoph Hellwig
2022-12-22 16:23 ` 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=Y63DQSUSW4aQlVJ+@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 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.