From: Christian Brauner <[email protected]>
To: Dmitry Kadashev <[email protected]>
Cc: Jens Axboe <[email protected]>,
Alexander Viro <[email protected]>,
Pavel Begunkov <[email protected]>,
Christoph Hellwig <[email protected]>,
[email protected],
io-uring <[email protected]>
Subject: Re: [PATCH v3 1/2] fs: make do_mkdirat() take struct filename
Date: Fri, 14 May 2021 17:11:34 +0200 [thread overview]
Message-ID: <20210514151134.tefjju5sc4fmk2fq@wittgenstein> (raw)
In-Reply-To: <CAOKbgA7JM24D2iuCoVjRV=oC1LW8JCcUMeAWMvFr1GHxb7T57g@mail.gmail.com>
On Thu, May 13, 2021 at 02:45:39PM +0700, Dmitry Kadashev wrote:
> On Thu, Apr 15, 2021 at 9:09 PM Christian Brauner
> <[email protected]> wrote:
> > Hm, I get your point but if you e.g. look at fs/exec.c we already do
> > have that problem today:
> >
> > SYSCALL_DEFINE5(execveat,
> > int, fd, const char __user *, filename,
> > const char __user *const __user *, argv,
> > const char __user *const __user *, envp,
> > int, flags)
> > {
> > int lookup_flags = (flags & AT_EMPTY_PATH) ? LOOKUP_EMPTY : 0;
> >
> > return do_execveat(fd,
> > getname_flags(filename, lookup_flags, NULL),
> > argv, envp, flags);
> > }
> >
> > The new simple flag helper would simplify things because right now it
> > pretends that it cares about multiple flags where it actually just cares
> > about whether or not empty pathnames are allowed and it forces callers
> > to translate between flags too.
>
> Hi Christian,
>
> Sorry for the long silence, I got overwhelmed by the primary job and life
> stuff. I've finally carved out some time to work on this. I left out the
No problem at all! Yeah, I can relate. :)
> "make getname_flags accept a single boolean instead of flags" bit to
> make the change smaller. If you think it's something that definitely
> should be in this patch set then let me know, I'll put it back in. I'm
> still somewhat concerned about the separation of the capability check
> and the actual logic to get the name, but I guess I'll just post what I
> have and collect comments.
Sounds good!
Christian
next prev parent reply other threads:[~2021-05-14 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 5:59 [PATCH v3 0/2] io_uring: add mkdirat support Dmitry Kadashev
2021-03-30 5:59 ` [PATCH v3 1/2] fs: make do_mkdirat() take struct filename Dmitry Kadashev
2021-03-30 7:17 ` Christian Brauner
2021-03-31 10:43 ` Dmitry Kadashev
2021-04-08 8:45 ` Dmitry Kadashev
2021-04-15 7:14 ` Dmitry Kadashev
2021-04-15 10:08 ` Christian Brauner
2021-04-15 10:09 ` Christian Brauner
2021-04-15 10:41 ` Dmitry Kadashev
2021-04-15 14:09 ` Christian Brauner
2021-05-13 7:45 ` Dmitry Kadashev
2021-05-14 15:11 ` Christian Brauner [this message]
2021-03-30 5:59 ` [PATCH v3 2/2] io_uring: add support for IORING_OP_MKDIRAT Dmitry Kadashev
2021-03-31 1:31 ` Al Viro
2021-03-31 10:38 ` Dmitry Kadashev
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=20210514151134.tefjju5sc4fmk2fq@wittgenstein \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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