From: Miklos Szeredi <miklos@szeredi.hu>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Amir Goldstein <amir73il@gmail.com>,
David Howells <dhowells@redhat.com>,
Yu-li Lin <yulilin@google.com>,
Chirantan Ekbote <chirantan@chromium.org>
Subject: Re: [PATCH v3 3/9] vfs: add tmpfile_open() helper
Date: Wed, 21 Sep 2022 16:33:07 +0200 [thread overview]
Message-ID: <CAJfpegvYKV5ViNMev+zieH5Zu4uYGHNjjOzT2R7ZHvnwevLmTA@mail.gmail.com> (raw)
In-Reply-To: <20220921080902.wbjbsrlwj3frrot3@wittgenstein>
On Wed, 21 Sept 2022 at 10:09, Christian Brauner <brauner@kernel.org> wrote:
>
> Feels like this could be simplified while being equally legible to
> something like:
>
> /**
> * tmpfile_open - open a tmpfile for kernel internal use
> * @mnt_userns: user namespace of the mount the inode was found from
> * @parentpath: path of the base directory
> * @mode: mode of the new tmpfile
> * @open_flag: flags
> * @cred: credentials for open
> *
> * Create and open a temporary file. The file is not accounted in nr_files,
> * hence this is only for kernel internal use, and must not be installed into
> * file tables or such.
> *
> * The helper relies on the "noaccount" property of open_with_fake_path().
> * Otherwise it is equivalent to dentry_open().
> *
> * Return: Opened tmpfile on success, error pointer on failure.
> */
> struct file *tmpfile_open(struct user_namespace *mnt_userns,
> const struct path *parentpath,
> umode_t mode, int open_flag, const struct cred *cred)
> {
> struct file *file;
> int error;
> struct path path = { .mnt = parentpath->mnt };
>
> path.dentry = vfs_tmpfile(mnt_userns, parentpath->dentry, mode, open_flag);
> if (IS_ERR(path.dentry))
> return ERR_CAST(path.dentry);
>
> error = may_open(mnt_userns, &path, 0, open_flag);
> if (!error)
> file = open_with_fake_path(&path, open_flag, d_inode(path.dentry), cred);
> else
> file = ERR_PTR(error);
> dput(path.dentry);
> return file;
> }
> EXPORT_SYMBOL(tmpfile_open);
Okay, but this code gets completely rewritten in 7/9, so maybe not
worth bothering about.
Thanks,
Miklos
next prev parent reply other threads:[~2022-09-21 14:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 19:36 [PATCH v3 0/9] fuse tmpfile Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 1/9] cachefiles: tmpfile error handling cleanup Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 2/9] hugetlbfs: cleanup mknod and tmpfile Miklos Szeredi
2022-09-21 7:59 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 3/9] vfs: add tmpfile_open() helper Miklos Szeredi
2022-09-21 8:09 ` Christian Brauner
2022-09-21 14:33 ` Miklos Szeredi [this message]
2022-09-20 19:36 ` [PATCH v3 4/9] cachefiles: use " Miklos Szeredi
2022-09-21 8:26 ` Christian Brauner
2022-09-21 14:44 ` Miklos Szeredi
2022-09-21 19:46 ` Al Viro
2022-09-22 8:04 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 5/9] ovl: " Miklos Szeredi
2022-09-21 8:35 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 6/9] vfs: make vfs_tmpfile() static Miklos Szeredi
2022-09-21 8:36 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 7/9] vfs: move open right after ->tmpfile() Miklos Szeredi
2022-09-20 20:57 ` Al Viro
2022-09-21 3:06 ` Miklos Szeredi
2022-09-21 8:54 ` Christian Brauner
2022-09-21 14:53 ` Miklos Szeredi
2022-09-21 19:55 ` Al Viro
2022-09-21 9:03 ` Christian Brauner
2022-09-21 14:56 ` Miklos Szeredi
2022-09-21 15:09 ` Christian Brauner
2022-09-21 15:24 ` Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 8/9] vfs: open inside ->tmpfile() Miklos Szeredi
2022-09-21 9:08 ` Christian Brauner
2022-09-21 14:58 ` Miklos Szeredi
2022-09-21 15:07 ` Christian Brauner
2022-09-21 15:27 ` Miklos Szeredi
2022-09-21 15:36 ` Christian Brauner
2022-09-21 19:52 ` Al Viro
2022-09-20 19:36 ` [PATCH v3 9/9] fuse: implement ->tmpfile() Miklos Szeredi
2022-09-21 9:15 ` Christian Brauner
2022-09-21 15:00 ` Miklos Szeredi
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=CAJfpegvYKV5ViNMev+zieH5Zu4uYGHNjjOzT2R7ZHvnwevLmTA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chirantan@chromium.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yulilin@google.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).