From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>, Anuj Gupta <anuj20.g@samsung.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: in-kernel verification of user PI?
Date: Fri, 31 Jan 2025 11:36:25 +0100 [thread overview]
Message-ID: <20250131103625.GA20115@lst.de> (raw)
In-Reply-To: <3e7a79d7-b5ed-4ad2-a2d2-84c2c6cda757@samsung.com>
On Fri, Jan 31, 2025 at 04:04:53PM +0530, Kanchan Joshi wrote:
> On 1/29/2025 6:16 PM, Christoph Hellwig wrote:
> > Also another thing is that right now the holder of a path or fd has no
> > idea what metadata it is supposed to pass. For block device special
> > files find the right sysfs directory is relatively straight forward
> > (but still annoying), but one a file is on a file systems that becomes
> > impossible. I think we'll need an ioctl that exposes the equivalent
> > of the integrity sysfs directory to make this usable by applications.
>
> Are you thinking this ioctl to be on a regular file?
On anything that supports passing PI through io_uring. So block devices
and (some) regular files.
prev parent reply other threads:[~2025-01-31 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250129124655epcas5p39750f07e5015f1dd5e198c72cca0aa4e@epcas5p3.samsung.com>
2025-01-29 12:46 ` in-kernel verification of user PI? Christoph Hellwig
2025-01-29 14:23 ` Martin K. Petersen
2025-01-29 15:26 ` Christoph Hellwig
2025-01-29 15:42 ` Martin K. Petersen
2025-01-29 15:43 ` Christoph Hellwig
2025-01-29 16:15 ` Martin K. Petersen
2025-01-30 13:02 ` Christoph Hellwig
2025-01-31 10:34 ` Kanchan Joshi
2025-01-31 10:36 ` Christoph Hellwig [this message]
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=20250131103625.GA20115@lst.de \
--to=hch@lst.de \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.