All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Valentin Zaharov" <karlos_@netvision.net.il>
Cc: <linux-kernel@vger.kernel.org>, "Steven French" <sfrench@us.ibm.com>
Subject: Re: cifs causes BUG: soft lockup detected on CPU
Date: Thu, 29 Mar 2007 02:21:31 -0700	[thread overview]
Message-ID: <20070329022131.e5e48c53.akpm@linux-foundation.org> (raw)
In-Reply-To: <58D14E53A4F69C4EAF4D29171C447CC4011AC783@NTX-CL.forest.netvision.net.il>

On Thu, 29 Mar 2007 11:13:04 +0200 "Valentin Zaharov" <karlos_@netvision.net.il> wrote:

> I've tried different kernel versions.
> Right now iam using generic 2.6.9-42 on one machine and 2.6.20.1 on
> another one.
> I also tried various distributions ( Suse, CentOS, RHEL4 ) - not sure it
> is relevant.
> Tried installing latest cifs modules, tried changing CIFSMaxBufSize to
> 15000,  without luck.
> Freezes are totally random - sometimes they happen 2-4 times a day,
> sometimes it can take 2 weeks.

Yeah, it's a relatively recently known-bug, I'm afraid.

Probably this will keep you out of trouble until it gets fixed
for real:

--- a/include/linux/fs.h~a
+++ a/include/linux/fs.h
@@ -627,25 +627,7 @@ extern void inode_double_unlock(struct i
  */
 static inline loff_t i_size_read(const struct inode *inode)
 {
-#if BITS_PER_LONG==32 && defined(CONFIG_SMP)
-	loff_t i_size;
-	unsigned int seq;
-
-	do {
-		seq = read_seqcount_begin(&inode->i_size_seqcount);
-		i_size = inode->i_size;
-	} while (read_seqcount_retry(&inode->i_size_seqcount, seq));
-	return i_size;
-#elif BITS_PER_LONG==32 && defined(CONFIG_PREEMPT)
-	loff_t i_size;
-
-	preempt_disable();
-	i_size = inode->i_size;
-	preempt_enable();
-	return i_size;
-#else
 	return inode->i_size;
-#endif
 }
 
 /*
_


  reply	other threads:[~2007-03-29  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29  9:13 cifs causes BUG: soft lockup detected on CPU Valentin Zaharov
2007-03-29  9:21 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01 19:38 Steve French (smfltc)
2007-04-01  8:02 Valentin Zaharov
2007-03-29 15:42 Valentin Zaharov
2007-03-29  9:35 Valentin Zaharov
2007-03-29  8:32 Valentin Zaharov
2007-03-28 18:35 Valentin Zaharov
2007-03-29  8:54 ` Andrew Morton
2007-03-29 15:06   ` Steven 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=20070329022131.e5e48c53.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=karlos_@netvision.net.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@us.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.