From: Anuj Gupta <anuj20.g@samsung.com>
To: Keith Busch <kbusch@meta.com>
Cc: hch@lst.de, axboe@kernel.dk, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, martin.petersen@oracle.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] blk-integrity: remove seed for user mapped buffers
Date: Thu, 17 Oct 2024 11:31:23 +0530 [thread overview]
Message-ID: <20241017060123.GA8191@green245> (raw)
In-Reply-To: <20241016201309.1090320-1-kbusch@meta.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Wed, Oct 16, 2024 at 01:13:09PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> The seed is only used for kernel generation and verification. That
> doesn't happen for user buffers, so passing the seed around doesn't
> accomplish anything.
>
Not for nvme passthrough, but all this code is needed for io_uring
metadata series. Please see the need/justifcation [*].
[*] https://lore.kernel.org/linux-block/20241017054900.alfiqn3o37f4kkxb@green245/
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2024-10-17 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241016201330epcas5p33226adcbff73f7df7cced504aea64a13@epcas5p3.samsung.com>
2024-10-16 20:13 ` [PATCH] blk-integrity: remove seed for user mapped buffers Keith Busch
2024-10-17 5:57 ` Christoph Hellwig
2024-10-17 6:01 ` Anuj Gupta [this message]
2024-10-17 8:21 ` Christoph Hellwig
2024-10-29 11:57 ` Anuj Gupta
2024-10-30 13:38 ` Kanchan Joshi
2024-10-30 13:47 ` Jens Axboe
2024-10-30 13:50 ` Jens Axboe
2024-10-30 13:59 ` Kanchan Joshi
2024-10-30 14:01 ` Keith Busch
2024-10-30 13:49 ` 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=20241017060123.GA8191@green245 \
--to=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.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).