From: Jeff Layton <jlayton@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: Jan Seiffert <kaffeemonster@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sfrench@us.ibm.com, linux-cifs@vger.kernel.org
Subject: Re: [3.0.0+][Regression][Bisected] CIFS: getdents() broken for large dirs
Date: Tue, 2 Aug 2011 17:43:37 -0400 [thread overview]
Message-ID: <20110802174337.70a4ff15@tlielax.poochiereds.net> (raw)
In-Reply-To: <CAH2r5mvTtsDVaYWYswo+CgFRRZJ-+hWTca-3V9vZP7wh0ezfyw@mail.gmail.com>
On Tue, 2 Aug 2011 11:03:28 -0500
Steve French <smfrench@gmail.com> wrote:
> your patch does look right.
>
Sigh...as is often the case, things are not quite so simple...
I did some auditing of how server->maxBuf is used in the cifs code and
found it to be very confused. The reason it basically works, I think is
because on NEGOTIATE, the client does this:
server->maxBuf = min(le32_to_cpu(pSMBr->MaxBufferSize),
(__u32) CIFSMaxBufSize + MAX_CIFS_HDR_SIZE);
So using maxBuf and CIFSMaxBufSize interchangeably like the code does
is basically OK, even if it is confusing to limit how much the client
can receive based on how much the server can.
I think that we really need to approach this more comprehensively and
have a clear delineation between server->maxBuf and CIFSMaxBufSize. I
don't think it would be wise though to put that into 3.1 at this point.
I think it would probably be best to just back out commit c4d3396b2 for
now, and I'll plan to do this as a larger (and hopefully better-tested)
patchset for 6.2.
Sound ok? Do you need me to send a revert patch?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2011-08-02 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 0:30 Jan Seiffert
2011-08-02 10:44 ` Jeff Layton
2011-08-02 16:00 ` Jeff Layton
2011-08-02 16:03 ` Steve French
2011-08-02 21:43 ` Jeff Layton [this message]
2011-08-02 21:49 ` Steve French
2011-08-02 21:40 ` Jan Seiffert
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=20110802174337.70a4ff15@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=kaffeemonster@googlemail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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
all inboxes | Powered by JetHome®