[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUXsOexKcj+K_v_bsW6DkGFgyNOaEs_qVOAcdNGBbEb2w@mail.gmail.com>
Date: Fri, 27 Jul 2018 12:42:20 -0700
From: Andy Lutomirski <luto@...capital.net>
To: David Howells <dhowells@...hat.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Linux API <linux-api@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 29/38] vfs: syscall: Add fsconfig() for configuring and
managing a context [ver #10]
On Fri, Jul 27, 2018 at 10:34 AM, David Howells <dhowells@...hat.com> wrote:
> (*) fsconfig_set_path: A non-empty path is specified. The parameter must
> be expecting a path object. value points to a NUL-terminated string
> that is the path and aux is a file descriptor at which to start a
> relative lookup or AT_FDCWD.
>
> (*) fsconfig_set_path_empty: As fsconfig_set_path, but with AT_EMPTY_PATH
> implied.
>
> (*) fsconfig_set_fd: An open file descriptor is specified. value must
> be NULL and aux indicates the file descriptor.
Unless I'm rather confused, you have two or possibly three ways to
pass in an open fd. Can you clarify what the difference is and/or
remove all but one of them?
Powered by blists - more mailing lists