Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Tony Solomonik <tony.solomonik@gmail.com>
Cc: willy@infradead.org, axboe@kernel.dk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v8 1/2] Add do_ftruncate that truncates a struct file
Date: Mon, 29 Jan 2024 16:39:18 +0100	[thread overview]
Message-ID: <20240129-freischaffend-gefeuert-18ccf4cd5f01@brauner> (raw)
In-Reply-To: <20240129151507.14885-2-tony.solomonik@gmail.com>

On Mon, Jan 29, 2024 at 05:15:06PM +0200, Tony Solomonik wrote:
> do_sys_ftruncate receives a file descriptor, fgets the struct file, and
> finally actually truncates the file.
> 
> do_ftruncate allows for passing in a file directly, with the caller
> already holding a reference to it.
> 
> Signed-off-by: Tony Solomonik <tony.solomonik@gmail.com>
> ---
>  fs/internal.h |  1 +
>  fs/open.c     | 52 ++++++++++++++++++++++++++++-----------------------
>  2 files changed, 30 insertions(+), 23 deletions(-)
> 
> diff --git a/fs/internal.h b/fs/internal.h
> index 58e43341aebf..d35b1c05cf6d 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 do_ftruncate(struct file *file, loff_t length);
>  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..6d608ff4a3f7 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -154,49 +154,55 @@ 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 do_ftruncate(struct file *file, loff_t length)
>  {
>  	struct inode *inode;
>  	struct dentry *dentry;
> +	int error;
> +
> +	dentry = file->f_path.dentry;
> +	inode = dentry->d_inode;
> +	if (!S_ISREG(inode->i_mode) || !(file->f_mode & FMODE_WRITE))
> +		return -EINVAL;
> +
> +	/* Check IS_APPEND on real upper inode */
> +	if (IS_APPEND(file_inode(file)))
> +		return -EPERM;
> +	sb_start_write(inode->i_sb);
> +	error = security_file_truncate(file);
> +	if (!error)
> +		error = do_truncate(file_mnt_idmap(file), dentry, length,
> +				    ATTR_MTIME | ATTR_CTIME, file);
> +	sb_end_write(inode->i_sb);
> +
> +	return error;
> +}
> +
> +long do_sys_ftruncate(unsigned int fd, loff_t length, int small)
> +{
>  	struct fd f;
>  	int error;
>  
> -	error = -EINVAL;
>  	if (length < 0)
> -		goto out;
> -	error = -EBADF;
> +		return -EINVAL;
>  	f = fdget(fd);
>  	if (!f.file)
> -		goto out;
> +		return -EBADF;
>  
>  	/* explicitly opened as large or we are on 64-bit box */
>  	if (f.file->f_flags & O_LARGEFILE)
>  		small = 0;

Why is the O_LARGEFILE handling not needed when used from io_uring?

  parent reply	other threads:[~2024-01-29 15:39 UTC|newest]

Thread overview: 32+ 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
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
2024-01-26 15:21 ` [PATCH v6 " Tony Solomonik
2024-01-26 15:21   ` [PATCH v6 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-26 15:34     ` Matthew Wilcox
2024-01-26 15:21   ` [PATCH v6 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-26 15:57 ` [PATCH v7 0/2] " Tony Solomonik
2024-01-26 15:57   ` [PATCH v7 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-28 23:50     ` kernel test robot
2024-01-29  0:50     ` Matthew Wilcox
2024-01-26 15:57   ` [PATCH v7 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-29 15:15 ` [PATCH v8 0/2] " Tony Solomonik
2024-01-29 15:15   ` [PATCH v8 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-29 15:32     ` Matthew Wilcox
2024-01-29 15:39     ` Christian Brauner [this message]
     [not found]       ` <CAD62OrETm04q5F7ef8fpB5xF_vTKEHfas5W86QEssZ2ozyg0DQ@mail.gmail.com>
2024-02-01 23:20         ` Jens Axboe
2024-02-01 23:54           ` Matthew Wilcox
2024-01-29 15:15   ` [PATCH v8 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-02-02 12:17 ` [PATCH v9 0/2] " Tony Solomonik
2024-02-02 12:17   ` [PATCH v9 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-02-08 15:07     ` Jens Axboe
2024-02-09 10:22       ` Christian Brauner
2024-02-02 12:17   ` [PATCH v9 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-02-09 16:46   ` [PATCH v9 0/2] " Jens Axboe
     [not found]     ` <CAD62OrGiBX5YuKr_qRzCXPR5Cx_0Vw3Dei9f95Qww1rL45ejdA@mail.gmail.com>
2024-02-09 16:55       ` 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=20240129-freischaffend-gefeuert-18ccf4cd5f01@brauner \
    --to=brauner@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tony.solomonik@gmail.com \
    --cc=willy@infradead.org \
    /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