From: Sasha Levin <sashal@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Yi Zhang <yi.zhang@redhat.com>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
stable@vger.kernel.org
Subject: Re: [PATCH stable only] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1
Date: Wed, 27 Mar 2019 12:16:58 -0400 [thread overview]
Message-ID: <20190327161658.GL25262@sasha-vm> (raw)
In-Reply-To: <20190327090230.12671-1-ming.lei@redhat.com>
On Wed, Mar 27, 2019 at 05:02:30PM +0800, Ming Lei wrote:
>NVMe target only accepts single-page sg list, either file or block
>device backed target code follows this assumption.
>
>However, loop target is one exception, given the sg list is from
>the host queue directly.
>
>This patch sets loop queue's segment boundary mask as PAGE_SIZE - 1
>for following NVMe target assumption.
>
>Reported-by: Yi Zhang <yi.zhang@redhat.com>
>Fixes: 3a85a5de29ea ("nvme-loop: add a NVMe loopback host driver")
>Cc: Yi Zhang <yi.zhang@redhat.com>
>Cc: Sagi Grimberg <sagi@grimberg.me>
>Cc: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Ming Lei <ming.lei@redhat.com>
Could you provide some background as to why this is -stable only in the
commit message?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-03-27 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 9:02 [PATCH stable only] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1 Ming Lei
2019-03-27 16:16 ` Sasha Levin [this message]
2019-03-28 0:55 ` Ming Lei
2019-04-01 13:55 ` Greg KH
2019-04-02 1:05 ` Ming Lei
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=20190327161658.GL25262@sasha-vm \
--to=sashal@kernel.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=yi.zhang@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).