From: Puranjay Mohan <pjy@amazon.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
"Christoph Hellwig" <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<puranjay@kernel.org>
Subject: Re: [PATCH] nvme: check if the namespace supports metadata in nvme_map_user_request()
Date: Tue, 27 Aug 2024 12:28:45 +0000 [thread overview]
Message-ID: <mb61pjzg2gneq.fsf@amazon.com> (raw)
In-Reply-To: <20240827121955.GB1607@lst.de>
Christoph Hellwig <hch@lst.de> writes:
> On Tue, Aug 27, 2024 at 12:17:01PM +0000, Puranjay Mohan wrote:
>> + if (meta_buffer && meta_len && bdev && !blk_get_integrity(bdev->bd_disk))
>> + return -EINVAL;
>
> Overly long line here. If we go past my initial RFC I'd probably
> restructure the function a little bit, i.e. add a new
>
> bool has_metadata = bdev && meta_buffer && meta_len;
>
> and then use that both for the support check and the actualy mapping
> below.
Sure,
I will send v2 with these changes now.
P.S. - It looks like we will need manual backports for stable kernels as
this won't apply directly. I will send them after this is accepted.
Thanks,
Puranjay
next prev parent reply other threads:[~2024-08-27 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:17 [PATCH] nvme: check if the namespace supports metadata in nvme_map_user_request() Puranjay Mohan
2024-08-27 12:19 ` Christoph Hellwig
2024-08-27 12:28 ` Puranjay Mohan [this message]
2024-09-06 18:07 ` Keith Busch
2024-08-27 15:42 ` Keith Busch
2024-08-28 4:29 ` Christoph Hellwig
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=mb61pjzg2gneq.fsf@amazon.com \
--to=pjy@amazon.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=puranjay@kernel.org \
--cc=sagi@grimberg.me \
/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