From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH] nvme-fc: use blk_rq_nr_phys_segments
Date: Wed, 25 Jan 2017 09:58:03 +0100 [thread overview]
Message-ID: <20170125085803.GB3568@linux-x5ow.site> (raw)
In-Reply-To: <1484841357-17539-1-git-send-email-hch@lst.de>
On Thu, Jan 19, 2017@04:55:57PM +0100, Christoph Hellwig wrote:
> Without this deallocate won't work properly due to the mismatch
> of the bio/request size and the actual payload size.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
Might be worth adding a:
Fixes: f9d03f96b ('block: improve handling of the magic discard payload')
as well.
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-01-25 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 15:55 [PATCH] nvme-fc: use blk_rq_nr_phys_segments Christoph Hellwig
2017-01-25 8:46 ` Christoph Hellwig
2017-01-25 8:58 ` Johannes Thumshirn [this message]
2017-01-25 17:14 ` James Smart
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=20170125085803.GB3568@linux-x5ow.site \
--to=jthumshirn@suse.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