From: Christian Brauner <[email protected]>
To: Tony Solomonik <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH v5 1/2] Add ftruncate_file that truncates a struct file
Date: Thu, 25 Jan 2024 18:56:04 +0100 [thread overview]
Message-ID: <20240125-mickrig-gemustert-927a2eaee125@brauner> (raw)
In-Reply-To: <[email protected]>
On Wed, Jan 24, 2024 at 10:33:00AM +0200, Tony Solomonik wrote:
> do_sys_ftruncate receives a file descriptor, fgets the struct file, and
> finally actually truncates the file.
>
> ftruncate_file allows for passing in a file directly, with the caller
> already holding a reference to it.
>
> Signed-off-by: Tony Solomonik <[email protected]>
> ---
> fs/internal.h | 1 +
> fs/open.c | 53 +++++++++++++++++++++++++++------------------------
> 2 files changed, 29 insertions(+), 25 deletions(-)
>
> diff --git a/fs/internal.h b/fs/internal.h
> index 58e43341aebf..78a641ebd16e 100644
> --- a/fs/internal.h
> +++ b/fs/internal.h
> @@ -182,6 +182,7 @@ extern struct open_how build_open_how(int flags, umode_t mode);
> extern int build_open_flags(const struct open_how *how, struct open_flags *op);
> extern struct file *__close_fd_get_file(unsigned int fd);
>
> +long ftruncate_file(struct file *file, loff_t length, int small);
> long do_sys_ftruncate(unsigned int fd, loff_t length, int small);
> int chmod_common(const struct path *path, umode_t mode);
> int do_fchownat(int dfd, const char __user *filename, uid_t user, gid_t group,
> diff --git a/fs/open.c b/fs/open.c
> index 02dc608d40d8..649d38eecfe4 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -154,49 +154,52 @@ COMPAT_SYSCALL_DEFINE2(truncate, const char __user *, path, compat_off_t, length
> }
> #endif
>
> -long do_sys_ftruncate(unsigned int fd, loff_t length, int small)
> +long ftruncate_file(struct file *file, loff_t length, int small)
All internal functions that io_uring currently calls are called do_*():
* do_rmdir()
* do_unlinkat()
* do_mkdirat()
* do_symlinkat()
* do_statx()
So I'd follow that pattern and just call that thing do_ftruncate().
Otherwise looks good to me,
Acked-by: Christian Brauner <[email protected]>
next prev parent reply other threads:[~2024-01-25 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 8:32 [PATCH v5 0/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-24 8:33 ` [PATCH v5 1/2] Add ftruncate_file that truncates a struct file Tony Solomonik
2024-01-25 17:56 ` Christian Brauner [this message]
2024-01-25 18:01 ` Matthew Wilcox
2024-01-24 8:33 ` [PATCH v5 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-24 8:52 ` [PATCH v5 0/2] " Cedric Blancher
2024-01-24 12:52 ` Jens Axboe
2024-01-24 13:35 ` Cedric Blancher
2024-01-24 13:42 ` Jens Axboe
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=20240125-mickrig-gemustert-927a2eaee125@brauner \
[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