All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	autofs@linux.kernel.org
Subject: Re: Fix for SMP deadlock in autofs4
Date: Sat, 21 Apr 2001 00:04:40 -0700	[thread overview]
Message-ID: <20010421000439.B14074@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.31.0104202253010.15553-100000@penguin.transmeta.com> <Pine.GSO.4.21.0104210217000.23618-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0104210217000.23618-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sat, Apr 21, 2001 at 02:21:38AM -0400

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On Sat, Apr 21, 2001 at 02:21:38AM -0400, Alexander Viro wrote:
> Looks sane for me. However, I would add check for dentry being hashed and
> would skip the unhashed ones. Otherwise you can get a directory that
> had been removed but is still busy - doesn't look like a right thing to
> do. Jeremy?

It wouldn't hurt.  It can't happen in practice since unlink/rmdir happen
in very controlled ways (only the automount daemon is allowed to perform
those ops, so it will keep them in sync).

	J

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2001-04-21  7:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  8:49 Fix for SMP deadlock in autofs4 Jeremy Fitzhardinge
2001-04-20  9:00 ` Alexander Viro
2001-04-20  9:11   ` Jeremy Fitzhardinge
2001-04-20 19:01 ` Linus Torvalds
2001-04-20 19:53   ` Alexander Viro
2001-04-21  1:46     ` Jeremy Fitzhardinge
2001-04-21  5:59       ` Linus Torvalds
2001-04-21  6:21         ` Alexander Viro
2001-04-21  7:04           ` Jeremy Fitzhardinge [this message]
2001-04-21  7:02         ` Jeremy Fitzhardinge

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=20010421000439.B14074@goop.org \
    --to=jeremy@goop.org \
    --cc=autofs@linux.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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.