From: Stefan Roesch <[email protected]>
To: Pavel Begunkov <[email protected]>,
<[email protected]>, <[email protected]>
Subject: Re: [PATCH v1 1/3] fs: add parameter use_fpos to iterate_dir function
Date: Thu, 25 Nov 2021 15:19:29 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/25/21 7:55 AM, Pavel Begunkov wrote:
> On 11/23/21 18:10, Stefan Roesch wrote:
>> This adds the use_fpos parameter to the iterate_dir function.
>> If use_fpos is true it uses the file position in the file
>> structure (existing behavior). If use_fpos is false, it uses
>> the pos in the context structure.
>>
>> This change is required to support getdents in io_uring.
>>
>> Signed-off-by: Stefan Roesch <[email protected]>
>> ---
>> fs/exportfs/expfs.c | 2 +-
>> fs/nfsd/nfs4recover.c | 2 +-
>> fs/nfsd/vfs.c | 2 +-
>> fs/overlayfs/readdir.c | 6 +++---
>> fs/readdir.c | 28 ++++++++++++++++++++--------
>> include/linux/fs.h | 2 +-
>> 6 files changed, 27 insertions(+), 15 deletions(-)
>>
> [...]
>> diff --git a/fs/readdir.c b/fs/readdir.c
>> index 09e8ed7d4161..8ea5b5f45a78 100644
>> --- a/fs/readdir.c
>> +++ b/fs/readdir.c
>> @@ -21,6 +21,7 @@
>> #include <linux/unistd.h>
>> #include <linux/compat.h>
>> #include <linux/uaccess.h>
>> +#include "internal.h"
>> #include <asm/unaligned.h>
>> @@ -36,8 +37,14 @@
>> unsafe_copy_to_user(dst, src, len, label); \
>> } while (0)
>> -
>> -int iterate_dir(struct file *file, struct dir_context *ctx)
>> +/**
>> + * iterate_dir - iterate over directory
>> + * @file : pointer to file struct of directory
>> + * @ctx : pointer to directory ctx structure
>> + * @use_fpos: true : use file offset
>> + * false: use pos in ctx structure
>> + */
>> +int iterate_dir(struct file *file, struct dir_context *ctx, bool use_fpos)
>> {
>> struct inode *inode = file_inode(file);
>> bool shared = false;
>> @@ -60,12 +67,17 @@ int iterate_dir(struct file *file, struct dir_context *ctx)
>> res = -ENOENT;
>> if (!IS_DEADDIR(inode)) {
>> - ctx->pos = file->f_pos;
>> + if (use_fpos)
>> + ctx->pos = file->f_pos;
>
> One more thing I haven't noticed before, should pos be sanitised
> somehow if passed from the userspace? Do filesystems handle it
> well?
>
I checked a couple of filesystems and they all check that the pos value is reasonable.
>
>> +
>> if (shared)
>> res = file->f_op->iterate_shared(file, ctx);
>> else
>> res = file->f_op->iterate(file, ctx);
>> - file->f_pos = ctx->pos;
>> +
>> + if (use_fpos)
>> + file->f_pos = ctx->pos;
>> +
>> fsnotify_access(file);
>> file_accessed(file);
>> }
>
>
next prev parent reply other threads:[~2021-11-25 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 18:10 [PATCH v1 0/3] io_uring: add getdents64 support Stefan Roesch
2021-11-23 18:10 ` [PATCH v1 1/3] fs: add parameter use_fpos to iterate_dir function Stefan Roesch
2021-11-24 19:58 ` kernel test robot
2021-11-25 14:45 ` Miklos Szeredi
2021-11-25 23:18 ` Stefan Roesch
2021-11-25 15:47 ` Pavel Begunkov
2021-11-25 23:17 ` Stefan Roesch
2021-11-25 15:55 ` Pavel Begunkov
2021-11-25 23:19 ` Stefan Roesch [this message]
2021-11-23 18:10 ` [PATCH v1 2/3] fs: split off vfs_getdents function of getdents64 syscall Stefan Roesch
2021-11-26 10:53 ` Christian Brauner
2021-11-23 18:10 ` [PATCH v1 3/3] io_uring: add support for getdents64 Stefan Roesch
2021-11-25 15:41 ` Pavel Begunkov
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 \
[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