From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jeff Layton <jlayton@samba.org>
Cc: "J. R. Okajima" <hooanon05@yahoo.co.jp>,
Jesper Juhl <jj@chaosbits.net>,
linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org
Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2
Date: Thu, 18 Aug 2011 09:15:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108180914180.7903@p34.internal.lan> (raw)
In-Reply-To: <20110818091140.385a9455@barsoom.rdu.redhat.com>
On Thu, 18 Aug 2011, Jeff Layton wrote:
> On Thu, 18 Aug 2011 08:22:44 -0400 (EDT)
> Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>> Justin.
>>
>
> To be clear -- incoming in this case is reads or writes?
Reading from the CIFS share (Windows 7).
>
> Up until 3.0 cifs.ko didn't parallelize writes from a single thread. In
> 3.0 I added a patchset to increase the allowable wsize and to allow the
> kernel to issue writes in parallel.
Ahh, good to know, have not tried writes yet.
>
> Reads still suffer from the same problem however. I'm working on a
> patchset that should do the same thing for them, but it requires a
> fairly substantial overhaul of the receive codepaths.
Ok, that explains it then, thanks.
One other item, the rsync is currently running, what does mean/what option
would fix it/make the error go away?
[ 3730.897554] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3755.727255] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3760.509489] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3760.786650] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3762.854706] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3763.052163] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3764.962962] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3765.460372] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3765.855425] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3767.677672] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3781.958450] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3800.493896] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3805.911191] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3806.121384] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3817.356127] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3825.148050] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3833.687886] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3834.199746] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3834.448342] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3866.848508] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3867.126729] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3868.428427] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3872.206396] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3872.812745] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3877.655580] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3880.718684] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3880.769545] CIFS VFS: did not end path lookup where expected namelen is 0
[ 3882.026917] CIFS VFS: did not end path lookup where expected namelen is 0
Justin.
next prev parent reply other threads:[~2011-08-18 13:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 9:10 Kernel 3.0: Instant kernel crash when mounting CIFS Justin Piszcz
2011-08-15 9:18 ` Jesper Juhl
2011-08-15 10:47 ` Jeff Layton
2011-08-15 10:54 ` Justin Piszcz
2011-08-15 18:01 ` Justin Piszcz
2011-08-15 18:09 ` Steve French
2011-08-15 19:31 ` Dave Jones
2011-08-17 19:16 ` Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Justin Piszcz
[not found] ` <alpine.DEB.2.02.1108171545190.5877@p34.internal.lan>
2011-08-17 19:47 ` Justin Piszcz
2011-08-17 20:13 ` Jeff Layton
2011-08-17 20:45 ` Justin Piszcz
2011-08-17 21:11 ` Arnaud Lacombe
2011-08-17 21:53 ` Justin Piszcz
2011-08-17 22:13 ` Justin Piszcz
2011-08-17 22:18 ` Justin Piszcz
2011-08-17 23:31 ` Valdis.Kletnieks
2011-08-18 3:19 ` J. R. Okajima
2011-08-18 10:35 ` Justin Piszcz
2011-08-18 12:14 ` Justin Piszcz
2011-08-18 12:22 ` Justin Piszcz
2011-08-18 13:11 ` Jeff Layton
2011-08-18 13:15 ` Justin Piszcz [this message]
2011-08-18 17:04 ` Jeff Layton
2011-08-18 17:15 ` Steve French
2011-08-18 17:16 ` Justin Piszcz
2011-08-18 17:25 ` Steve French
2011-08-18 17:33 ` Justin Piszcz
2011-08-18 17:43 ` Steve French
2011-08-18 18:18 ` Justin Piszcz
2011-08-18 18:52 ` Jeff Layton
2011-08-18 18:54 ` Justin Piszcz
2011-08-18 19:02 ` Steve French
2011-08-26 21:59 ` Jeff Layton
2011-08-26 22:57 ` Justin Piszcz
2011-08-26 23:05 ` Steve French
2011-08-26 23:16 ` Justin Piszcz
2011-08-27 14:31 ` Jeff Layton
2011-08-18 17:36 ` Kong Li
2011-08-18 18:33 ` Jeff Layton
2011-08-18 14:19 ` J. R. Okajima
2011-08-18 16:01 ` Steve French
2011-08-18 16:02 ` Steve French
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=alpine.DEB.2.02.1108180914180.7903@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=hooanon05@yahoo.co.jp \
--cc=jj@chaosbits.net \
--cc=jlayton@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
/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®