From: "Aurélien Aptel" <aurelien.aptel@gmail.com>
To: Ronnie Sahlberg <lsahlber@redhat.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
Steve French <smfrench@gmail.com>
Subject: Re: [PATCH] cifs: fix skipping to incorrect offset in emit_cached_dirents
Date: Sun, 9 Oct 2022 19:54:45 +0200 [thread overview]
Message-ID: <CA+5B0FM0t5vF8oHCbhc8Cj3vQ6eUas3WPFH7d0RmqC2c+TRAbQ@mail.gmail.com> (raw)
In-Reply-To: <20221006043609.1193398-2-lsahlber@redhat.com>
Hi,
Make sure you're not re-introducing the bug where the first few files
are missing when mounting the root of a Windows drive.
See fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs/smb2ops.c?id=0595751f267994c3c7027377058e4185b3a28e75
And bug https://bugzilla.samba.org/show_bug.cgi?id=13107
Cheers,
next prev parent reply other threads:[~2022-10-09 17:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-10-10 5:12 ` ronnie 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-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-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
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=CA+5B0FM0t5vF8oHCbhc8Cj3vQ6eUas3WPFH7d0RmqC2c+TRAbQ@mail.gmail.com \
--to=aurelien.aptel@gmail.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).