From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents
Date: Tue, 11 Oct 2022 06:42:50 +1000 [thread overview]
Message-ID: <20221010204250.1411858-2-lsahlber@redhat.com> (raw)
In-Reply-To: <20221010204250.1411858-1-lsahlber@redhat.com>
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.
Also change cifs_filldir() to return -EEXIST when we encouter a dot-directory in the
reply from the server. Check for this in the caller and skip caching the entry and
skip incprementing ctx->pos or else we end up emitting a sequence of directory entries with
holes in the ctx->pos space.
Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
---
fs/cifs/readdir.c | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/fs/cifs/readdir.c b/fs/cifs/readdir.c
index 8e060c00c969..0c71a771b256 100644
--- a/fs/cifs/readdir.c
+++ b/fs/cifs/readdir.c
@@ -847,14 +847,14 @@ 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;
- ctx->pos = dirent->pos;
rc = dir_emit(ctx, dirent->name, dirent->namelen,
dirent->fattr.cf_uniqueid,
dirent->fattr.cf_dtype);
if (!rc)
return rc;
+ ctx->pos++;
}
return true;
}
@@ -965,7 +965,7 @@ static int cifs_filldir(char *find_entry, struct file *file,
/* skip . and .. since we added them first */
if (cifs_entry_is_dot(&de, file_info->srch_inf.unicode))
- return 0;
+ return -EEXIST;
if (file_info->srch_inf.unicode) {
struct nls_table *nlt = cifs_sb->local_nls;
@@ -1183,6 +1183,17 @@ int cifs_readdir(struct file *file, struct dir_context *ctx)
*tmp_buf = 0;
rc = cifs_filldir(current_entry, file, ctx,
tmp_buf, max_len, cfid);
+ /*
+ * If we got a dot directory, just skip to the next entry.
+ * We have already emitted it.
+ */
+ if (rc == -EEXIST) {
+ current_entry =
+ nxt_dir_entry(current_entry, end_of_smb,
+ cifsFile->srch_inf.info_level);
+ rc = 0;
+ continue;
+ }
if (rc) {
if (rc > 0)
rc = 0;
@@ -1202,10 +1213,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);
--
2.35.3
next prev parent reply other threads:[~2022-10-10 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 20:42 cifs: fix bug when skipping one entry too many after lseek() Ronnie Sahlberg
2022-10-10 20:42 ` Ronnie Sahlberg [this message]
-- 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-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
2022-10-11 21:38 ` Steve French
2022-10-11 21:54 ` 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=20221010204250.1411858-2-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--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).