Re: 2.6.22.1 Oops in put_nfs_open_context

On Mon, 2007-08-06 at 11:45 -0700, Andrew Morton wrote:
On Mon, 06 Aug 2007 14:19:54 -0400 Trond Myklebust <trond.myklebust@xxxxxxxxxx> wrote:

On Mon, 2007-08-06 at 11:01 -0700, Andrew Morton wrote:
On Mon, 6 Aug 2007 11:08:13 +0100 "Dr. David Alan Gilbert" <linux@xxxxxxxxxxx> wrote:

The oops below is from one of a pair of machines that run compiles;
they're not managing to stay up for more than a day or two at a time
this is the first time I've actually managed to capture an oops from one.
They lock to the point where they still ping, and they won't toggle
capslock. A top left running on them showed it sitting with pdflush
using 99% CPU.

Config at the bottom. The hardware are supermicro X7DVA boards with
2x Xeon 5140's. (These Supermicro bios don't appear to have the PCI-Express
coalesce option being discussed in another thread).


...

I believe this fix should address it.

Neat, and that's already in 2.6.23-rc2. Please consider sending something
to stable@xxxxxxxxxx when the dust has settled. David, it would be great if
we could get confirmation, please..

I haven't pushed it to Linus yet, but it might already be in -mm? I'm
planning a merge of a half-dozen fixes as soon as I get the last couple
of confirmations from the people testing them.

From: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Subject: No Subject
Date: Thu, 26 Jul 2007 12:06:17 -0400

We need to grab the inode->i_lock atomically with the last reference put in
order to remove the open context that is being freed from the
nfsi->open_files list.

Your patches have lost their titles btw.

Sorry about that. Evolution appears to "recognise" the patches as
emails, and gets confused...

Cheers
Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.security)
  • Re: Windows security patches
    ... If you have experiencing this problem for the first time in the fields then I do not envy you. ... > updating in-field images with latest microsoft updates and patches. ... > get patch information for some updates. ...
    (microsoft.public.windowsxp.embedded)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... the security bulletins, linked to by PA Bear in his post, discuss the vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... a developer may introduce one or more bugs ... each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
Loading