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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 15 Aug 2011 14:01:12 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Jeff Layton <jlayton@...ba.org>
cc:	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



On Mon, 15 Aug 2011, Justin Piszcz wrote:

>
>
> On Mon, 15 Aug 2011, Jeff Layton wrote:
>
>> On Mon, 15 Aug 2011 11:18:38 +0200 (CEST)
>> Jesper Juhl <jj@...osbits.net> wrote:
>> 
>> There was at least one known oops at mount time with 3.0:
>>
>>    https://bugzilla.redhat.com/show_bug.cgi?id=727927
>> 
>> ...but I can't tell whether you hit that w/o seeing the oops messasge.
>> 
>> It should be fixed in mainline and the patches for that and another
>> mount time problem will be in the next set of stable kernels. You may
>> want to pull these two commits into your kernel and try again:
>> 
>> 80975d21aae2136ccae1ce914a1602dc1d8b0795
>> f9e8c45002cacad536b338dfa9e910e341a49c31
>> 
>
> Thanks,
>
> Patches applied to 3.0.1 and will try to mount the CIFS shares later today:
>
> # patch -p1 < /home/war/cifs1
> patching file fs/cifs/cifsfs.c
> # patch -p1 < /home/war/cifs2
> patching file fs/cifs/inode.c
>
> Justin.
>
>

Hello,

It crashed again with the patches, this time I got a picture:
http://home.comcast.net/~jpiszcz/20110815/26030-kernel-crash-when-cifs-mount.jpg

The machine is up no issues until you try and mount a CIFS share, then
the problem occurs, every time (and with the patches as well).

3.0.1+80975d21aae2136ccae1ce914a1602dc1d8b0795
      +f9e8c45002cacad536b338dfa9e910e341a49c31

Same result.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ