From: Lachlan McIlroy <lachlan@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: [PATCH] XFS: Check for valid transaction headers in recovery
Date: Mon, 06 Oct 2008 14:14:50 +1000 [thread overview]
Message-ID: <48E990BA.3080306@sgi.com> (raw)
In-Reply-To: <20080924034120.GG5448@disturbed>
Looks fine now Dave.
Dave Chinner wrote:
> On Tue, Sep 23, 2008 at 10:07:56PM -0500, Eric Sandeen wrote:
>> Dave Chinner wrote:
>>> When we are about to add a new item to a transaction in recovery,
>>> we need to check that it is valid first. Current we just assert
>>> that header magic number matches, but in production systems
>>> that is not done add a corrupted transaction to the list to be
>>> processed. This results in a kernel oops later when processing the
>>> corrupted transaction.
>>>
>>> Instead, if we detect a corrupted transaction, abort recovery and
>>> leave the user to clean up the mess that has occurred.
>>>
>>> Signed-off-by: Dave Chinner <david@fromorbit.com>
>> Seems fine to me (I guess you tried the provided corrupt image?)
>
> Yes, I tried to mount it.
>
>> but the
>> commit message could be made a bit more ... English ;)
>
> Right. Updated patch (description) below ;)
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2008-10-06 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 1:16 [PATCH] XFS: Check for valid transaction headers in recovery Dave Chinner
2008-09-24 3:07 ` Eric Sandeen
2008-09-24 3:41 ` Dave Chinner
2008-10-06 4:14 ` Lachlan McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 21:57 Dave Chinner
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=48E990BA.3080306@sgi.com \
--to=lachlan@sgi.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