| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Aug 2011 09:15:36 -0400 (EDT) From: Justin Piszcz <jpiszcz@...idpixels.com> To: Jeff Layton <jlayton@...ba.org> cc: "J. R. Okajima" <hooanon05@...oo.co.jp>, Jesper Juhl <jj@...osbits.net>, linux-kernel@...r.kernel.org, Alan Piszcz <ap@...arrain.com>, Steve French <sfrench@...ba.org>, linux-cifs@...r.kernel.org Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 On Thu, 18 Aug 2011, Jeff Layton wrote: > On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) > Justin Piszcz <jpiszcz@...idpixels.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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists