From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752729Ab1HOSBR (ORCPT ); Mon, 15 Aug 2011 14:01:17 -0400 Received: from lucidpixels.com ([72.73.18.11]:47780 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752636Ab1HOSBN (ORCPT ); Mon, 15 Aug 2011 14:01:13 -0400 Date: Mon, 15 Aug 2011 14:01:12 -0400 (EDT) From: Justin Piszcz To: Jeff Layton cc: Jesper Juhl , linux-kernel@vger.kernel.org, Alan Piszcz , Steve French , linux-cifs@vger.kernel.org Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS In-Reply-To: Message-ID: References: <20110815064734.403b630f@corrin.poochiereds.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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.