mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Jeff Layton <jlayton@samba.org>, 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: Wed, 17 Aug 2011 19:31:09 -0400	[thread overview]
Message-ID: <26399.1313623869@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 17 Aug 2011 15:16:40 EDT." <alpine.DEB.2.02.1108171515050.5877@p34.internal.lan>

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

On Wed, 17 Aug 2011 15:16:40 EDT, Justin Piszcz said:

> Tried with linux-3.1-rc2 and:
> 
> You don't even need to get a successful mount:
> 
> Does anyone know if any kernel supports CIFS w/out crashing? I'd like to 
> backup some CIFS shares, thanks.

3.1.0-rc1-next-20110808 is talking CIFS to our NetApp without any complaint.
Not heavily stress tested, but it mounted, I can see files, I can open files, I
specifically tried 'df' and didn't crash.

So I'm guessing there's some subtle difference between what my NetApp feeds my
laptop over the wire and what you're seeing from your Windows box?


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2011-08-17 23:32 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 [this message]
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
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=26399.1313623869@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=ap@solarrain.com \
    --cc=jj@chaosbits.net \
    --cc=jlayton@samba.org \
    --cc=jpiszcz@lucidpixels.com \
    --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®