Re: Kernel 3.0: Instant kernel crash when mounting CIFS

[Steve French]

With the more current cifs (ie  patches applied) does it fail on the
mount? or after the mount on the df -h that you mentioned in your
earlier note?

Not immediately obvious to me if the oops has much to do with cifs
code given the call stack, but we may be able to determine a little
more by looking at a wireshark trace of the last network request
and/or response (presumably parsing a cifs QFSInfo response from
Windows 7).

I also run Windows 7 64 server in our test environment, will rebuild
on laster 3.0.1-rc2 and retry but I would be surprised if I can
reproduce this.

On Mon, Aug 15, 2011 at 1:01 PM, Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> wrote:
>
>
> 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@xxxxxxxxxxxxx> 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.
>
>



-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/