From: Jason Gunthorpe <jgg@nvidia.com>
To: Yan Zhao <yan.y.zhao@intel.com>
Cc: Yi Liu <yi.l.liu@intel.com>, "Tian, Kevin" <kevin.tian@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"ajones@ventanamicro.com" <ajones@ventanamicro.com>
Subject: Re: [PATCH] vfio: Reuse file f_inode as vfio device inode
Date: Wed, 10 Jul 2024 11:40:44 -0300 [thread overview]
Message-ID: <20240710144044.GA1482543@nvidia.com> (raw)
In-Reply-To: <ZoJDFyqzGVuntt94@yzhao56-desk.sh.intel.com>
On Mon, Jul 01, 2024 at 01:48:07PM +0800, Yan Zhao wrote:
> No, I don't have such a need.
> I just find it's confusing to say "Only the group path allows the device to be
> opened multiple times. The device cdev path doesn't have a secure way for it",
> since it's still doable to achieve the same "secure" level in cdev path and the
> group path is not that "secure" :)
It is more that the group path had an API that allowed for multiple
FDs without an actual need to ever use that. You can always make more
FDs with dup.
There is no reason for this functionality, we just have to keep it
working as a matter of uABI compatability and we are being more strict
in the new APIs.
Jason
next prev parent reply other threads:[~2024-07-10 14:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 9:53 [PATCH] vfio: Reuse file f_inode as vfio device inode Yan Zhao
2024-06-20 10:14 ` Yan Zhao
2024-06-26 8:36 ` Tian, Kevin
2024-06-26 9:11 ` Yan Zhao
2024-06-26 13:35 ` Jason Gunthorpe
2024-06-26 23:55 ` Tian, Kevin
2024-06-27 12:26 ` Jason Gunthorpe
2024-06-27 0:17 ` Tian, Kevin
2024-06-27 9:51 ` Yan Zhao
2024-06-27 12:42 ` Jason Gunthorpe
2024-06-28 5:21 ` Yan Zhao
2024-06-28 9:48 ` Yi Liu
2024-06-28 15:28 ` Yan Zhao
2024-06-30 7:06 ` Yi Liu
2024-07-01 1:47 ` Yan Zhao
2024-07-01 5:44 ` Yi Liu
2024-07-01 5:48 ` Yan Zhao
2024-07-10 14:40 ` Jason Gunthorpe [this message]
2024-07-12 5:19 ` Yan Zhao
2024-07-12 6:14 ` Yi Liu
2024-07-01 7:54 ` Yi Liu
2024-07-01 11:29 ` Yan Zhao
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=20240710144044.GA1482543@nvidia.com \
--to=jgg@nvidia.com \
--cc=ajones@ventanamicro.com \
--cc=alex.williamson@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=yan.y.zhao@intel.com \
--cc=yi.l.liu@intel.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