From: Tom Talpey <tom@talpey.com>
To: Ronnie Sahlberg <lsahlber@redhat.com>,
linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: Re: [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents
Date: Tue, 11 Oct 2022 12:38:47 -0400 [thread overview]
Message-ID: <f2d94342-c316-21d3-4dc8-7a969a102c2d@talpey.com> (raw)
In-Reply-To: <20221011064611.1428646-2-lsahlber@redhat.com>
On 10/11/2022 2:46 AM, Ronnie Sahlberg wrote:
> When application has done lseek() to a different offset on a directory fd
> we skipped one entry too many before we start emitting directory entries
> from the cache.
>
> We need to also make sure that when we are starting to emit directory
> entries from the cache, the ->pos sequence might have holes and skip
> some indices.
>
> Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
> ---
> fs/cifs/readdir.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/fs/cifs/readdir.c b/fs/cifs/readdir.c
> index 8e060c00c969..7170614434a1 100644
> --- a/fs/cifs/readdir.c
> +++ b/fs/cifs/readdir.c
> @@ -847,14 +847,19 @@ static bool emit_cached_dirents(struct cached_dirents *cde,
> int rc;
>
> list_for_each_entry(dirent, &cde->entries, entry) {
> - if (ctx->pos >= dirent->pos)
> + if (ctx->pos > dirent->pos)
> continue;
> + /*
> + * There may be holes in the ->pos sequence
> + * so always force ctx->pos to the current position.
> + */
The comment is a bit vague by referring to "->pos", because
it's the same name in both ctx and dirent.
But I have a second question, does squeezing out the holes
affect a later possible lseek on the dirhandle? I'm having
trouble tracking down where that might happen.
> ctx->pos = dirent->pos;
> rc = dir_emit(ctx, dirent->name, dirent->namelen,
> dirent->fattr.cf_uniqueid,
> dirent->fattr.cf_dtype);
> if (!rc)
> return rc;
It's weird that "rc" is an integer, but dir_emit() returns a bool.
It's also confusing that this isn't coded as
if (!rc)
return false;
Other than those questions, it looks like a clever fix.
Tom.
> + ctx->pos++;
> }
> return true;
> }
> @@ -1202,10 +1207,10 @@ int cifs_readdir(struct file *file, struct dir_context *ctx)
> ctx->pos, tmp_buf);
> cifs_save_resume_key(current_entry, cifsFile);
> break;
> - } else
> - current_entry =
> - nxt_dir_entry(current_entry, end_of_smb,
> - cifsFile->srch_inf.info_level);
> + }
> + current_entry =
> + nxt_dir_entry(current_entry, end_of_smb,
> + cifsFile->srch_inf.info_level);
> }
> kfree(tmp_buf);
>
next prev parent reply other threads:[~2022-10-11 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 6:46 cifs: fix skipping to incorrect offset in emit_cached_diretns Ronnie Sahlberg
2022-10-11 6:46 ` [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents Ronnie Sahlberg
2022-10-11 16:38 ` Tom Talpey [this message]
2022-10-11 21:38 ` Steve French
2022-10-11 21:54 ` ronnie sahlberg
-- strict thread matches above, loose matches on Subject: below --
2022-10-11 22:07 cifs: fix emitting cached direntries Ronnie Sahlberg
2022-10-11 22:07 ` [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents Ronnie Sahlberg
2022-10-12 0:49 ` Tom Talpey
2022-10-12 1:04 ` Leif Sahlberg
2022-10-10 20:42 cifs: fix bug when skipping one entry too many after lseek() Ronnie Sahlberg
2022-10-10 20:42 ` [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents Ronnie Sahlberg
2022-10-06 4:36 cifs: fix failure for generic/257 Ronnie Sahlberg
2022-10-06 4:36 ` [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents Ronnie Sahlberg
2022-10-06 5:18 ` Steve French
2022-10-06 5:21 ` Steve French
2022-10-08 15:21 ` Steve French
2022-10-09 17:54 ` Aurélien Aptel
2022-10-10 5:12 ` ronnie sahlberg
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=f2d94342-c316-21d3-4dc8-7a969a102c2d@talpey.com \
--to=tom@talpey.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=smfrench@gmail.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).