mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Piszcz <ap@solarrain.com>
Subject: Kernel 3.0: Instant kernel crash when mounting CIFS
Date: Mon, 15 Aug 2011 05:10:29 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1108150506310.7571@p34.internal.lan> (raw)

Hi,

Is this normal/is there a limitation on CIFS mounts? I do not have the 
full crash output, I would need to take a picture of the screen, but its 
completely reproducible, crashes every time..  thoughts?

Aug 14 05:16:41 box kernel: [518217.158195] df              D 0000000000000000     0  5465  11246 0x00000004
Aug 14 05:16:41 box kernel: [518217.158200]  ffff88061f19c090 0000000000000082 0000000000000002 ffff880600000000
Aug 14 05:16:41 box kernel: [518217.158206]  ffff8806275accf0 0000000000004000 ffff88058513ffd8 ffff88058513ffd8
Aug 14 05:16:41 box kernel: [518217.158211]  ffff88058513fdf8 ffff880627076240 000000000000002f 0000000000000000
Aug 14 05:16:41 box kernel: [518217.158217] Call Trace:
Aug 14 05:16:41 box kernel: [518217.158226]  [<ffffffff810ca086>] ? do_lookup+0x46/0x310
Aug 14 05:16:41 box kernel: [518217.158231]  [<ffffffff810c7e9d>] ? acl_permission_check+0x4d/0xb0
Aug 14 05:16:41 box kernel: [518217.158239]  [<ffffffff815b2448>] ? __mutex_lock_slowpath+0xc8/0x140
Aug 14 05:16:41 box kernel: [518217.158243]  [<ffffffff815b1fea>] ? mutex_lock+0x1a/0x40
Aug 14 05:16:41 box kernel: [518217.158250]  [<ffffffff811ec969>] ? cifs_reconnect_tcon+0x1a9/0x320
Aug 14 05:16:41 box kernel: [518217.158254]  [<ffffffff811ecba3>] ? smb_init+0x33/0x90
Aug 14 05:16:41 box kernel: [518217.158258]  [<ffffffff811f30e0>] ? CIFSSMBQFSInfo+0x60/0x210
Aug 14 05:16:41 box kernel: [518217.158262]  [<ffffffff811eb86e>] ? cifs_statfs+0xce/0x170
Aug 14 05:16:41 box kernel: [518217.158268]  [<ffffffff810e5797>] ? statfs_by_dentry+0x67/0x100
Aug 14 05:16:41 box kernel: [518217.158272]  [<ffffffff810e5845>] ? vfs_statfs+0x15/0x90
Aug 14 05:16:41 box kernel: [518217.158275]  [<ffffffff810e58f0>] ? user_statfs+0x30/0x50
Aug 14 05:16:41 box kernel: [518217.158279]  [<ffffffff810e5972>] ? sys_statfs+0x12/0x30
Aug 14 05:16:41 box kernel: [518217.158284]  [<ffffffff815b3b7b>] ? system_call_fastpath+0x16/0x1b

Then it hangs up, on my machine it actually panics and in both cases all I/O
stops and the machine is unusable.  This is from simply mounting a CIFS share.
The share sizes are 18T and 28T, is there a limitation on the size that would
cause the kernel to crash like that?

mount.cifs //l1/drve /mnt_pnt -o user=myusername,pass=mypassword, then
df -h or ls /mnt_pnt instant kernel panic. :(

Remote host is Windows 7 64-bit.

Justin.

             reply	other threads:[~2011-08-15  9:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  9:10 Justin Piszcz [this message]
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
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=alpine.DEB.2.02.1108150506310.7571@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=ap@solarrain.com \
    --cc=linux-kernel@vger.kernel.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®