Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] nvme/pci: Check segement valid for SGL use
Date: Mon, 15 Jan 2018 10:25:36 -0700	[thread overview]
Message-ID: <5bfb2835-15e0-2ec0-4b5f-68da3e3ee78c@kernel.dk> (raw)
In-Reply-To: <20180115172218.GA12251@lst.de>

On 1/15/18 10:22 AM, Christoph Hellwig wrote:
> On Mon, Jan 15, 2018@09:20:40AM -0700, Jens Axboe wrote:
>> On 1/15/18 9:01 AM, Christoph Hellwig wrote:
>>> Actually this needs to go into nvme-4.15.  The offending commit is
>>> only in 4.15-rc, and not in nvme-4.16 or Jens' for-4.16 tree.
>>
>> I can queue it up for 4.15, there's already been one report of
>> this...
> 
> I think we'll need at least another related fix as well.  I'll
> send you a pull request by tomorrow or so.

Sounds good, thanks.

-- 
Jens Axboe

      reply	other threads:[~2018-01-15 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 13:07 [PATCH] nvme/pci: Check segement valid for SGL use Keith Busch
2018-01-15 13:11 ` Paul Menzel
2018-01-15 15:21 ` Christoph Hellwig
2018-01-15 16:01 ` Christoph Hellwig
2018-01-15 16:20   ` Jens Axboe
2018-01-15 17:22     ` Christoph Hellwig
2018-01-15 17:25       ` Jens Axboe [this message]

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=5bfb2835-15e0-2ec0-4b5f-68da3e3ee78c@kernel.dk \
    --to=axboe@kernel.dk \
    /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