From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/4] nvmet: fix computation of io vector number
Date: Wed, 27 Mar 2019 09:15:49 +0100 [thread overview]
Message-ID: <20190327081549.GF20525@lst.de> (raw)
In-Reply-To: <CACVXFVNTOVcP7N_MCZ+JEUJX09WUH0Ds3yZ_DELrSkAfPEDrpg@mail.gmail.com>
On Tue, Mar 26, 2019@03:50:01PM +0800, Ming Lei wrote:
> On Tue, Mar 26, 2019@3:38 PM Christoph Hellwig <hch@lst.de> wrote:
> >
> > I'd rather see this merged with the last one (and patch 3 dropped as
> > it just gets removed entirely in 4) - that fixes all the issues together
> > and doesn't require your patch 1 as as a workaround first.
>
> Patch 1 isn't a workaround, which is needed for stable tree, and
> the other fixes won't work without patch 1.
>
> However, we may revert patch 1 for 5.1 in which multi-page bvec
> is supported.
Lets do it another way around - put the proper fix into 5.1-rc and
only apply patch 1 for stable. No need to put something in and
immediately revert it.
next prev parent reply other threads:[~2019-03-27 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 3:19 [PATCH 0/4] nvmet: fix file & block device backed ns Ming Lei
2019-03-26 3:19 ` [PATCH 1/4] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1 Ming Lei
2019-03-26 7:36 ` Christoph Hellwig
2019-03-26 7:37 ` Ming Lei
2019-03-26 7:39 ` Ming Lei
2019-03-27 8:15 ` Christoph Hellwig
2019-03-27 8:26 ` Ming Lei
2019-03-27 8:39 ` Christoph Hellwig
2019-03-26 3:19 ` [PATCH 2/4] nvmet: fix computation of io vector number Ming Lei
2019-03-26 7:38 ` Christoph Hellwig
2019-03-26 7:50 ` Ming Lei
2019-03-27 8:15 ` Christoph Hellwig [this message]
2019-03-26 3:19 ` [PATCH 3/4] nvmet: fix computation of bvec->bv_len Ming Lei
2019-03-26 3:19 ` [PATCH 4/4] nvmet: build bvec from sg directly 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=20190327081549.GF20525@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox