public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sungjong Seo" <sj1557.seo@samsung.com>
To: <linkinjeon@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"'Wang Yugui'" <wangyugui@e16-tech.com>
Subject: RE: [PATCH v1] exfat: fix unexpected EOF while reading dir
Date: Thu, 29 Dec 2022 11:25:58 +0900	[thread overview]
Message-ID: <019201d91b2c$e34ee610$a9ecb230$@samsung.com> (raw)
In-Reply-To: <PUZPR04MB6316182889B5CE8003A5324981EC9@PUZPR04MB6316.apcprd04.prod.outlook.com>

> If the position is not aligned with the dentry size, the return
> value of readdir() will be NULL and errno is 0, which means the
> end of the directory stream is reached.
> 
> If the position is aligned with dentry size, but there is no file
> or directory at the position, exfat_readdir() will continue to
> get dentry from the next dentry. So the dentry gotten by readdir()
> may not be at the position.
> 
> After this commit, if the position is not aligned with the dentry
> size, round the position up to the dentry size and continue to get
> the dentry.
> 
> Fixes: ca06197382bd ("exfat: add directory operations")
> 
> Signed-off-by: Yuezhang Mo <Yuezhang.Mo@sony.com>
> Reviewed-by: Andy Wu <Andy.Wu@sony.com>
> Reviewed-by: Aoyama Wataru <wataru.aoyama@sony.com>
> Reported-by: Wang Yugui <wangyugui@e16-tech.com>

Looks good. Thanks.

Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>

> ---
>  fs/exfat/dir.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/fs/exfat/dir.c b/fs/exfat/dir.c
> index 1dfa67f307f1..1122bee3b634 100644
> --- a/fs/exfat/dir.c
> +++ b/fs/exfat/dir.c
> @@ -234,10 +234,7 @@ static int exfat_iterate(struct file *file, struct
> dir_context *ctx)
>  		fake_offset = 1;
>  	}
> 
> -	if (cpos & (DENTRY_SIZE - 1)) {
> -		err = -ENOENT;
> -		goto unlock;
> -	}
> +	cpos = round_up(cpos, DENTRY_SIZE);
> 
>  	/* name buffer should be allocated before use */
>  	err = exfat_alloc_namebuf(nb);
> --
> 2.25.1


  reply	other threads:[~2022-12-29  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221226072359epcas1p4fa9052333561109f76db171f4c57324a@epcas1p4.samsung.com>
2022-12-26  7:23 ` [PATCH v1] exfat: fix unexpected EOF while reading dir Yuezhang.Mo
2022-12-29  2:25   ` Sungjong Seo [this message]
2022-12-30  1:33   ` Namjae Jeon

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='019201d91b2c$e34ee610$a9ecb230$@samsung.com' \
    --to=sj1557.seo@samsung.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangyugui@e16-tech.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