From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Fix nvme_get/set_features() with a NULL result pointer
Date: Thu, 25 Aug 2016 09:38:10 +0200 [thread overview]
Message-ID: <20160825073810.GA18622@lst.de> (raw)
In-Reply-To: <f0eca21161c9ec5f81e9591741463ec3883cb931.1472035881.git.luto@kernel.org>
Ooops, yes.
Are you looking into new nvme_set_features users? Another thing
we need to tackle is either replacing dma_addr argument with a
a real kernel pointer (or just kill it until users show up)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] nvme: Fix nvme_get/set_features() with a NULL result pointer
Date: Thu, 25 Aug 2016 09:38:10 +0200 [thread overview]
Message-ID: <20160825073810.GA18622@lst.de> (raw)
In-Reply-To: <f0eca21161c9ec5f81e9591741463ec3883cb931.1472035881.git.luto@kernel.org>
Ooops, yes.
Are you looking into new nvme_set_features users? Another thing
we need to tackle is either replacing dma_addr argument with a
a real kernel pointer (or just kill it until users show up)
next prev parent reply other threads:[~2016-08-25 7:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 10:52 [PATCH] nvme: Fix nvme_get/set_features() with a NULL result pointer Andy Lutomirski
2016-08-24 10:52 ` Andy Lutomirski
2016-08-24 11:04 ` Sagi Grimberg
2016-08-24 11:04 ` Sagi Grimberg
2016-08-24 14:11 ` Jens Axboe
2016-08-24 14:11 ` Jens Axboe
2016-08-25 7:38 ` Christoph Hellwig [this message]
2016-08-25 7:38 ` Christoph Hellwig
2016-08-25 7:54 ` Andy Lutomirski
2016-08-25 7:54 ` Andy Lutomirski
2016-08-25 8:27 ` Christoph Hellwig
2016-08-25 8:27 ` Christoph Hellwig
2016-08-25 14:20 ` Jens Axboe
2016-08-25 14:20 ` Jens Axboe
2016-08-26 14:31 ` Andy Lutomirski
2016-08-26 14:31 ` Andy Lutomirski
2016-08-26 14:35 ` Christoph Hellwig
2016-08-26 14:35 ` Christoph Hellwig
2016-08-26 15:17 ` Keith Busch
2016-08-26 15:17 ` Keith Busch
2016-08-26 15:12 ` Jens Axboe
2016-08-26 15:12 ` Jens Axboe
2016-08-26 15:06 ` Jens Axboe
2016-08-26 15:06 ` 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=20160825073810.GA18622@lst.de \
--to=hch@lst.de \
/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.