From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Rui Gomes <rgomes@rvx.is>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs_repair: junk last entry in sf dir if name starts beyond dir size
Date: Mon, 9 Mar 2015 21:17:45 -0400 [thread overview]
Message-ID: <20150310011745.GA2722@laptop.bfoster> (raw)
In-Reply-To: <54FDFEDC.5090106@sandeen.net>
On Mon, Mar 09, 2015 at 04:13:16PM -0400, Eric Sandeen wrote:
> When process_sf_dir2() is trying to salvage entries in a corrupted
> short form directory, it may attempt to shorten the last entry in
> the dir if it extends beyond the directory size.
>
> However, if the name already starts past the dir size, no amount
> of name-shortening will make it fit, but the code doesn't realize
> this. The namelen variable comes out to be negative, and things
> go downhill from there, resulting in a segfault when we try to
> memmove a negative number of bytes.
>
> If no amount of name-shortening can make the last dir entry fit
> in the dir size, simply junk the entry.
>
> Reported by: Rui Gomes <rgomes@rvx.is>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> This adds a bit more spaghetti to an existing pot, but I think
> it clearly fixes the problem; I might try to rework these cases
> to coalesce some of the code.
>
> (I also wonder about the tradeoff between shortening entries and
> increasing the dir size, but for now I'm just following the
> direction the repair code already takes).
>
Seems Ok on a first glance. The fix is associated with the specific
namelen calculation. Are we susceptible to a similar problem in the
previous branch where we also calculate namelen from the dir size (the
namelen == 0 case)? It looks like we could set a bad value there.
Brian
> diff --git a/repair/dir2.c b/repair/dir2.c
> index 6b8964d..308808d 100644
> --- a/repair/dir2.c
> +++ b/repair/dir2.c
> @@ -911,6 +911,20 @@ _("zero length entry in shortform dir %" PRIu64 ""),
> namelen = ino_dir_size -
> ((__psint_t) &sfep->name[0] -
> (__psint_t) sfp);
> + /* Entry name starts past size of dir; junk it */
> + if (namelen <= 0) {
> + do_warn(
> +_("start of last entry name overflows space left in in shortform dir %" PRIu64 ", "),
> + ino);
> + if (!no_modify)
> + do_warn(
> + _("junking entry #%d\n"), i);
> + else
> + do_warn(
> + _("would junk entry #%d\n"), i);
> + break;
> + }
> + /* Ok, truncate this entry to end of dir */
> do_warn(
> _("size of last entry overflows space left in in shortform dir %" PRIu64 ", "),
> ino);
>
> _______________________________________________
> 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-10 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 20:13 [PATCH] xfs_repair: junk last entry in sf dir if name starts beyond dir size Eric Sandeen
2015-03-10 1:17 ` Brian Foster [this message]
2015-03-10 13:27 ` Eric Sandeen
2015-03-10 15:43 ` Eric Sandeen
2015-03-10 17:27 ` Rui Gomes
2015-03-10 17:37 ` Eric Sandeen
2015-03-11 14:26 ` Rui Gomes
2015-03-11 14:44 ` Eric Sandeen
2015-03-11 15:04 ` Rui Gomes
2015-03-11 15:46 ` Eric Sandeen
2015-03-11 16:01 ` Rui Gomes
2015-04-09 10:42 ` Rui Gomes
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=20150310011745.GA2722@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=rgomes@rvx.is \
--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