From: Christoph Hellwig <hch@infradead.org>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: Christoph Hellwig <hch@infradead.org>,
Andras Korn <korn-sgi.com@chardonnay.math.bme.hu>,
xfs@oss.sgi.com
Subject: Re: xfs: prevent kernel crash due to corrupted inode log format
Date: Tue, 17 Feb 2009 04:31:47 -0500 [thread overview]
Message-ID: <20090217093147.GA15620@infradead.org> (raw)
In-Reply-To: <200902162135.20065.arekm@maven.pl>
On Mon, Feb 16, 2009 at 09:35:19PM +0100, Arkadiusz Miskiewicz wrote:
> On Sunday 15 of February 2009, Christoph Hellwig wrote:
> > Andras Korn reported an oops on log replay causes by a corrupted
>
> Where is that report? I'm wondering if it's the same issue as I'm seeing:
>
> http://pld.pastebin.com/f15430869
> http://pld.pastebin.com/fbcdce88
Not related at all.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-17 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 19:13 xfs: prevent kernel crash due to corrupted inode log format Christoph Hellwig
2009-02-16 20:35 ` Arkadiusz Miskiewicz
2009-02-17 9:31 ` Christoph Hellwig [this message]
2009-03-03 16:28 ` Eric Sandeen
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=20090217093147.GA15620@infradead.org \
--to=hch@infradead.org \
--cc=arekm@maven.pl \
--cc=korn-sgi.com@chardonnay.math.bme.hu \
--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 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.