Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 5.1
Date: Thu, 11 Apr 2019 17:31:34 +0200	[thread overview]
Message-ID: <20190411153134.GA16359@infradead.org> (raw)

Hi Jens,

two nvme fixes for 5.1 - fixing the initial CSN for nvme-fc, and handle
log page offsets properly in the target.

The following changes since commit a3761c3c91209b58b6f33bf69dd8bb8ec0c9d925:

  block: do not leak memory in bio_copy_user_iov() (2019-04-10 16:14:40 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.1

for you to fetch changes up to d808b7f759b50acf0784ce6230ffa63e12ef465d:

  nvmet: fix discover log page when offsets are used (2019-04-11 17:28:30 +0200)

----------------------------------------------------------------
James Smart (1):
      nvme-fc: correct csn initialization and increments on error

Keith Busch (1):
      nvmet: fix discover log page when offsets are used

 drivers/nvme/host/fc.c          | 20 +++++++++---
 drivers/nvme/target/admin-cmd.c |  5 +++
 drivers/nvme/target/discovery.c | 68 +++++++++++++++++++++++++++--------------
 drivers/nvme/target/nvmet.h     |  1 +
 include/linux/nvme.h            |  9 ++++--
 5 files changed, 73 insertions(+), 30 deletions(-)

             reply	other threads:[~2019-04-11 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 15:31 Christoph Hellwig [this message]
2019-04-11 15:37 ` [GIT PULL] nvme fixes for 5.1 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2019-03-28 17:19 Christoph Hellwig
2019-03-28 17:22 ` 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=20190411153134.GA16359@infradead.org \
    --to=hch@infradead.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