From: "Randolf Pohl" <randolf.pohl@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, stable@kernel.org
Subject: Re: [2.6.27] filesystem (ext3) corruption (access beyond end)
Date: Fri, 05 Dec 2008 10:46:39 +0100 [thread overview]
Message-ID: <20081205094639.8800@gmx.net> (raw)
I think, stable and gregkh should be CCed on this,
and yes, I guess this deserves some investigation.
Regards,
Randolf
http://lkml.org/lkml/2008/12/4/246
Folkert van Heusden wrote:
> Hi,
>
> With 2.6.26 and 2.6.27 a system of mine (a P4 with HT and IDE disk)
> gets massive disk-corruption: in dmesg warnings for access beyond
> drive end.
> Now this bug did not happen in 2.6.18 (debian kernel) and it seems to
> be gone in 2.6.28-rc* as well.
> My question now is: should it still be investigated?
>
>
> Folkert van Heusden
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
next reply other threads:[~2008-12-05 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 9:46 Randolf Pohl [this message]
2008-12-05 9:50 ` [resend] Re: [2.6.27] filesystem (ext3) corruption (access beyond end) Randolf Pohl
2008-12-06 15:53 ` Folkert van Heusden
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 17:01 Folkert van Heusden
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=20081205094639.8800@gmx.net \
--to=randolf.pohl@gmx.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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.