mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nick Piggin <npiggin@gmail.com>
Cc: "J. R. Okajima" <hooanon05@yahoo.co.jp>,
	Nick Piggin <npiggin@kernel.dk>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, u.kleine-koenig@pengutronix.de,
	"Ramirez Luna, Omar" <omar.ramirez@ti.com>
Subject: Re: [PATCH] fs: Work around NFS wreckage
Date: Fri, 14 Jan 2011 10:29:54 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1101141028350.2678@localhost6.localdomain6> (raw)
In-Reply-To: <AANLkTikjTqcTzBVNouMdb2-QDmEKvH0p_uZ-SE9aNW6f@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 840 bytes --]

On Fri, 14 Jan 2011, Nick Piggin wrote:

> On Fri, Jan 14, 2011 at 3:41 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Thu, 13 Jan 2011, J. R. Okajima wrote:
> >> Thomas Gleixner:
> >> > The dcache scalability work broke NFS root filesystems.
> >>       :::
> >> > Check for parent equal dentry and skip the nested lock to avoid the
> >> > deadlock. I'm sure this is the wrong fix, but at least it "works" :)
> >>
> >> With this patch, can you unmount it cleanly?
> >> It skips incrementing d_count for both dentries.
> >> Do we need at least one?
> >
> 
> Yeah thanks everyone for reporting this.
> 
> I have a fix for it in a slightly different way, and a couple of other reported
> bugs, which are going through stress testing now.

Can you point us to the patches, so we can run our own set of
tests in paralell?

Thanks,

	tglx

  reply	other threads:[~2011-01-14  9:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 13:54 Thomas Gleixner
2011-01-13 14:10 ` J. R. Okajima
2011-01-13 15:17   ` Uwe Kleine-König
2011-01-14  1:30     ` J. R. Okajima
2011-01-13 16:41   ` Thomas Gleixner
2011-01-14  1:01     ` Nick Piggin
2011-01-14  9:29       ` Thomas Gleixner [this message]
2011-01-14  9:47         ` Sedat Dilek
2011-01-14 15:47         ` Linus Torvalds
2011-01-14 16:40           ` Thomas Gleixner
2011-01-14 21:44             ` Nick Piggin
2011-01-13 14:12 ` Uwe Kleine-König

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.LFD.2.00.1101141028350.2678@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=hooanon05@yahoo.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=omar.ramirez@ti.com \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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®