From: Randy Dunlap <rdunlap@infradead.org>
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>,
miklos@szeredi.hu
Cc: Amir Goldstein <amir73il@gmail.com>,
Andrei Vagin <avagin@gmail.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
David Howells <dhowells@redhat.com>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] overlayfs: add ioctls that allows to get fhandle for layers dentries
Date: Sun, 4 Oct 2020 12:48:17 -0700 [thread overview]
Message-ID: <9cd0e9d1-f124-3f2d-86e6-e6e96a1ccb1e@infradead.org> (raw)
In-Reply-To: <20201004192401.9738-2-alexander.mikhalitsyn@virtuozzo.com>
On 10/4/20 12:24 PM, Alexander Mikhalitsyn wrote:
> +#define OVL_IOC_GETLWRFHNDLSNUM _IO('o', 1)
> +// DISCUSS: what if MAX_HANDLE_SZ will change?
> +#define OVL_IOC_GETLWRFHNDL _IOR('o', 2, struct ovl_mnt_opt_fh)
> +#define OVL_IOC_GETUPPRFHNDL _IOR('o', 3, struct ovl_mnt_opt_fh)
> +#define OVL_IOC_GETWRKFHNDL _IOR('o', 4, struct ovl_mnt_opt_fh)
Hi,
This needs to have Documentation/userspace-api/ioctl/ioctl-number.rst
updated also.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-10-04 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 19:24 [RFC PATCH 0/1] overlayfs: C/R enhancments (RFC) Alexander Mikhalitsyn
2020-10-04 19:24 ` [RFC PATCH 1/1] overlayfs: add ioctls that allows to get fhandle for layers dentries Alexander Mikhalitsyn
2020-10-04 19:48 ` Randy Dunlap [this message]
2020-10-05 7:56 ` [RFC PATCH 0/1] overlayfs: C/R enhancments (RFC) Amir Goldstein
2020-10-05 19:46 ` Alexander Mikhalitsyn
2020-10-06 6:53 ` Amir Goldstein
2020-10-05 17:02 ` [RFC PATCH] overlayfs: add OVL_IOC_GETINFOFD ioctl that opens ovlinfofd Alexander Mikhalitsyn
2020-10-05 17:08 ` Randy Dunlap
2020-10-05 17:12 ` Alexander Mikhalitsyn
2020-10-05 17:22 ` Amir Goldstein
2020-10-05 19:39 ` Alexander Mikhalitsyn
2020-10-06 9:54 ` Miklos Szeredi
2020-10-14 14:14 ` [RFC PATCH] overlayfs: add fsinfo(FSINFO_ATTR_OVL_SOURCES) support Alexander Mikhalitsyn
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=9cd0e9d1-f124-3f2d-86e6-e6e96a1ccb1e@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=amir73il@gmail.com \
--cc=avagin@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ptikhomirov@virtuozzo.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).