From: Theodore Tso <tytso@mit.edu>
To: Jim Garlick <garlick@llnl.gov>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs - e2fsck pass1c does extra work if root dir has shared blocks
Date: Fri, 20 Apr 2007 08:14:57 -0400 [thread overview]
Message-ID: <20070420121457.GA18529@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0704101538020.31519@webb>
On Tue, Apr 10, 2007 at 03:39:56PM -0700, Jim Garlick wrote:
>
> Another small bug I think: if the root directory contains shared
> blocks, e2fsck pass1c search_dirent_proc() will be looking for
> one more containing directory than it will ever find, and thus
> loses an opportunity to terminate early.
>
> Signed-off-by: Jim Garlick <garlick@llnl.gov>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2007-04-20 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 20:51 [PATCH] e2fsprogs - pass1c terminates early if hard links Jim Garlick
2007-04-10 22:39 ` [PATCH] e2fsprogs - e2fsck pass1c does extra work if root dir has shared blocks Jim Garlick
2007-04-20 12:14 ` Theodore Tso [this message]
2007-04-11 3:40 ` [PATCH] e2fsprogs - pass1c terminates early if hard links Theodore Tso
2007-04-11 4:22 ` Andreas Dilger
2007-04-11 10:42 ` Theodore Tso
2007-04-11 11:51 ` Andreas Dilger
2007-04-11 12:57 ` Theodore Tso
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=20070420121457.GA18529@thunk.org \
--to=tytso@mit.edu \
--cc=garlick@llnl.gov \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).