From: "Theodore Ts'o" <tytso@mit.edu>
To: Alexander Viro <viro@math.psu.edu>
Cc: Christopher Li <chrisl@vmware.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Ext2 devel <ext2-devel@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix bug in ext3 htree rename: doesn't delete old name, leaves ino with bad nlink
Date: Wed, 6 Nov 2002 21:44:42 -0500 [thread overview]
Message-ID: <20021107024442.GA11010@think.thunk.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0211061746410.10405-100000@steklov.math.psu.edu>
On Wed, Nov 06, 2002 at 05:47:40PM -0500, Alexander Viro wrote:
>
> HUH?
>
> ->rename() holds ->i_sem on both directories. So do all other directory
> methods. What the hell is going on there?
What's going on is that had a brain-fart, and forgot about inode
semaphore that's held by the VFS layer. Chris, sorry about that;
there is no need retry multiple times. We only need to retry once, in
the case where the node gets split.
- Ted
next prev parent reply other threads:[~2002-11-07 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 4:47 bug in ext3 htree rename: doesn't delete old name, leaves ino with bad nlink Jeremy Fitzhardinge
2002-11-05 21:24 ` [Ext2-devel] " chrisl
2002-11-06 5:02 ` Jeremy Fitzhardinge
2002-11-06 8:25 ` [PATCH] Fix " chrisl
2002-11-06 8:44 ` Andrew Morton
2002-11-06 21:40 ` Theodore Ts'o
2002-11-07 1:24 ` Christopher Li
2002-11-06 22:41 ` Theodore Ts'o
2002-11-06 22:47 ` Alexander Viro
2002-11-07 2:44 ` Theodore Ts'o [this message]
2002-11-07 1:58 ` Christopher Li
2002-11-06 23:27 ` [Ext2-devel] " Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 5:40 [PATCH] Fix bug in ext3 htree rename: doesn't delete old name , " Christopher Li
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=20021107024442.GA11010@think.thunk.org \
--to=tytso@mit.edu \
--cc=chrisl@vmware.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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.