From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 3/4] xfs_repair: collapse 2 cases in process_sf_dir2
Date: Fri, 13 Mar 2015 10:35:44 -0400 [thread overview]
Message-ID: <20150313143544.GF2678@laptop.bfoster> (raw)
In-Reply-To: <54FF5C4F.80709@sandeen.net>
On Tue, Mar 10, 2015 at 05:04:15PM -0400, Eric Sandeen wrote:
> process_sf_dir2() has 2 cases for a bad namelen: on-disk namelen
> is 0, or on-disk namelen extends beyond the directory i_size.
>
> After the prior 2 patches, the code for each case is now essentially
> the same, so collapse the two cases.
>
> Note, this does slightly change some of the error messages.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> diff --git a/repair/dir2.c b/repair/dir2.c
> index 7aede6a..5512e41 100644
> --- a/repair/dir2.c
> +++ b/repair/dir2.c
> @@ -861,36 +861,44 @@ process_sf_dir2(
> _("entry \"%*.*s\" in shortform directory %" PRIu64 " references %s inode %" PRIu64 "\n"),
> namelen, namelen, sfep->name, ino, junkreason,
> lino);
> - if (namelen == 0) {
> - /*
> - * if we're really lucky, this is
> - * the last entry in which case we
> - * can use the dir size to set the
> - * namelen value. otherwise, forget
> - * it because we're not going to be
> - * able to find the next entry.
> - */
> +
> + /* is dir namelen 0 or does this entry extend past dir size? */
> + if (namelen == 0) {
> + junkreason = _("is zero length");
> bad_sfnamelen = 1;
> + } else if ((__psint_t) sfep - (__psint_t) sfp +
> + xfs_dir3_sf_entsize(mp, sfp, sfep->namelen)
> + > ino_dir_size) {
> + junkreason = _("extends past end of dir");
> + bad_sfnamelen = 1;
> + }
>
> + if (bad_sfnamelen) {
> + /*
> + * if we're really lucky, this is the last entry in
"... in which case ..."
(irrelevant as this is removed by the next patch)
Reviewed-by: Brian Foster <bfoster@redhat.com>
> + * case we can use the dir size to set the namelen
> + * value. otherwise, forget it because we're not going
> + * to be able to find the next entry.
> + */
> if (i == num_entries - 1) {
> namelen = ino_dir_size -
> ((__psint_t) &sfep->name[0] -
> (__psint_t) sfp);
> if (!no_modify) {
> do_warn(
> -_("zero length entry in shortform dir %" PRIu64 ", resetting to %d\n"),
> - ino, namelen);
> +_("entry #%d %s in shortform dir %" PRIu64 ", resetting to %d\n"),
> + i, junkreason, ino, namelen);
> sfep->namelen = namelen;
> *dino_dirty = 1;
> } else {
> do_warn(
> -_("zero length entry in shortform dir %" PRIu64 ", would set to %d\n"),
> - ino, namelen);
> +_("entry #%d %s in shortform dir %" PRIu64 ", would set to %d\n"),
> + i, junkreason, ino, namelen);
> }
> } else {
> do_warn(
> -_("zero length entry in shortform dir %" PRIu64 ""),
> - ino);
> +_("entry #%d %s in shortform dir %" PRIu64),
> + i, junkreason, ino);
> if (!no_modify)
> do_warn(_(", junking %d entries\n"),
> num_entries - i);
> @@ -903,39 +911,6 @@ _("zero length entry in shortform dir %" PRIu64 ""),
> */
> break;
> }
> - } else if ((__psint_t) sfep - (__psint_t) sfp +
> - xfs_dir3_sf_entsize(mp, sfp, sfep->namelen)
> - > ino_dir_size) {
> - bad_sfnamelen = 1;
> -
> - if (i == num_entries - 1) {
> - namelen = ino_dir_size -
> - ((__psint_t) &sfep->name[0] -
> - (__psint_t) sfp);
> - do_warn(
> -_("size of last entry overflows space left in in shortform dir %" PRIu64 ", "),
> - ino);
> - if (!no_modify) {
> - do_warn(_("resetting to %d\n"),
> - namelen);
> - sfep->namelen = namelen;
> - *dino_dirty = 1;
> - } else {
> - do_warn(_("would reset to %d\n"),
> - namelen);
> - }
> - } else {
> - do_warn(
> -_("size of entry #%d overflows space left in in shortform dir %" PRIu64 "\n"),
> - i, ino);
> - if (!no_modify)
> - do_warn(_("junking %d entries\n"),
> - num_entries - i);
> - else
> - do_warn(_("would junk %d entries\n"),
> - num_entries - i);
> - break;
> - }
> }
>
> /*
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-03-13 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 20:53 [PATCH 0/4] xfs_repair: clean up process_sf_dir2 Eric Sandeen
2015-03-10 20:55 ` [PATCH 1/4] xfs_repair: dirty inode in process_sf_dir2 if we change namelen Eric Sandeen
2015-03-13 14:34 ` Brian Foster
2015-03-10 21:01 ` [PATCH 2/4] xfs_repair: remove impossible tests in process_sf_dir2 Eric Sandeen
2015-03-13 14:34 ` Brian Foster
2015-03-10 21:04 ` [PATCH 3/4] xfs_repair: collapse 2 cases " Eric Sandeen
2015-03-13 14:35 ` Brian Foster [this message]
2015-03-10 21:11 ` [PATCH 4/4] xfs_repair: remove last-entry hack " Eric Sandeen
2015-03-13 14:41 ` Brian Foster
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=20150313143544.GF2678@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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