From: Arjan van de Ven <arjanv@redhat.com>
To: Chris Caputo <ccaputo@alt.net>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: inode_unused list corruption in 2.4.26 - spin_lock problem?
Date: Sat, 3 Jul 2004 07:15:34 +0200 [thread overview]
Message-ID: <20040703051534.GA4998@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407021231040.22597-100000@nacho.alt.net>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Fri, Jul 02, 2004 at 01:00:19PM -0700, Chris Caputo wrote:
> On Fri, 25 Jun 2004, Marcelo Tosatti wrote:
> > On Wed, Jun 23, 2004 at 06:50:48PM -0700, Chris Caputo wrote:
> > > Is it safe to assume that the x86 version of atomic_dec_and_lock(), which
> > > iput() uses, is well trusted? I figure it's got to be, but doesn't hurt
> > > to ask.
> >
> > Pretty sure it is, used all over. You can try to use non-optimize version
> > at lib/dec_and_lock.c for a test.
>
> My current theory is that occasionally when irqbalance changes CPU
> affinities that the resulting set_ioapic_affinity() calls somehow cause
> either inter-CPU locking or cache coherency or ??? to fail.
or.... some spinlock is just incorrect and having the irqbalance irqlayout
unhides that.. irqbalance only balances very very rarely so I doubt it's the
cause of anything...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-03 5:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 0:47 inode_unused list corruption in 2.4.26 - spin_lock problem? Chris Caputo
2004-06-20 0:15 ` Marcelo Tosatti
2004-06-20 3:33 ` Trond Myklebust
2004-06-21 0:45 ` Marcelo Tosatti
2004-06-21 17:10 ` Trond Myklebust
2004-06-21 18:23 ` Marcelo Tosatti
2004-06-24 1:51 ` Chris Caputo
2004-06-25 7:47 ` Chris Caputo
2004-06-24 1:50 ` Chris Caputo
2004-06-25 8:04 ` Chris Caputo
2004-06-25 10:18 ` Chris Caputo
2004-06-25 12:17 ` Marcelo Tosatti
2004-07-02 20:00 ` Chris Caputo
2004-07-03 5:15 ` Arjan van de Ven [this message]
2004-07-26 17:41 ` Chris Caputo
2004-07-27 14:19 ` Marcelo Tosatti
2004-07-27 16:08 ` Chris Caputo
2004-07-29 0:25 ` Marcelo Tosatti
2004-07-29 6:27 ` Chris Caputo
2004-07-29 7:54 ` Arjan van de Ven
2004-07-29 10:57 ` Marcelo Tosatti
2004-07-29 12:21 ` Arjan van de Ven
2004-07-29 16:22 ` Chris Caputo
2004-07-29 16:23 ` Arjan van de Ven
2004-08-04 15:38 ` Chris Caputo
2004-08-04 18:47 ` Chris Caputo
[not found] <20040805225549.GA18420@logos.cnet>
2004-08-07 16:00 ` Chris Caputo
2004-08-07 18:31 ` Marcelo Tosatti
2004-08-07 19:36 ` Marcelo Tosatti
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=20040703051534.GA4998@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=ccaputo@alt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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.