mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Ville Herva <vherva@niksula.hut.fi>, linux-kernel@vger.kernel.org
Cc: sak@iki.fi, phillips@innominate.de, viro@math.psu.edu,
	alan@lxorguk.ukuu.org.uk, tao@acc.umu.se
Subject: Re: Ext2 groups descriptor corruption in 2.2 - Phillips's patch seems to work
Date: Wed, 2 Jan 2002 12:42:54 +0100	[thread overview]
Message-ID: <E16LjnL-00010c-00@starship.berlin> (raw)
In-Reply-To: <20020101152802.A1331@niksula.cs.hut.fi>
In-Reply-To: <20020101152802.A1331@niksula.cs.hut.fi>

On January 1, 2002 02:28 pm, Ville Herva wrote:
> A while ago Daniel Phillips posted a patch for 2.4.0-test11 to cure groups
> descriptor corruption in ext2.
> 
> The corruption had been seen with 2.2 and 2.0 for a long time. It happens
> most likely in situations where there are many hard links to same inode (see
> first report below).
> 
> I gather this fix has gone into 2.4 mainline in different form (see Al
> Viro's fix below). It never went to 2.2 (nor 2.0) afaik.
> 
> The fix applies pretty cleanly to 2.2.20, and has been tested by me and
> Samuli Kärkkäinen (again, see first problem report) for about a month now.
> Samuli reports that he had been able to reproduce the bug in about 10-15
> backup runs with unpatched 2.2.18. With the patch applied, it hasn't
> appeared in well over 20 runs. My experience is similar with 2.2.20.
> 
> I haven't tested the patch on 2.0, but the problem seems to exists in 2.0 as
> well. Taking a quick look, it seems the patch can be applied to 2.0.40pre3
> with minor tweaking (s/ext2_get_group_desc/get_group_desc/g, remove
> le16_to_cpu() from patch, and perhaps the add the additional get_group_desc
> return value error checking to 2.0 ialloc.c that 2.2 has.)
> 
> Alan, David, perhaps this would be worth applying to next 2.2/2.0 pre? Al,
> Daniel, what do you think? Should the patch be tidied up before 2.2
> inclusion (as was done for 2.4)?

Since you have done such a thorough job of documenting the whole thing, why 
not drop the other shoe and submit the patches?

--
Daniel

  reply	other threads:[~2002-01-02 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01 13:28 Ville Herva
2002-01-02 11:42 ` Daniel Phillips [this message]
2002-01-02 11:53   ` Alan Cox
2002-01-04  0:00     ` Andreas Dilger
2002-01-04  7:36       ` Ville Herva

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=E16LjnL-00010c-00@starship.berlin \
    --to=phillips@bonn-fries.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@innominate.de \
    --cc=sak@iki.fi \
    --cc=tao@acc.umu.se \
    --cc=vherva@niksula.hut.fi \
    --cc=viro@math.psu.edu \
    /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

all inboxes | Powered by JetHome®