Messages in this thread | | | From | GertJan Spoelman <> | Subject | Re: 2.4.20-rc3 ext3 fsck corruption -- tool update warning needed? | Date | Fri, 29 Nov 2002 00:47:35 +0100 |
| |
On Thursday 28 November 2002 23:49, Andries Brouwer wrote: > On Wed, Nov 27, 2002 at 07:55:48AM -0500, Theodore Ts'o wrote: > > Ah, ha. I think I know what happened. > > > > What version of e2fsprogs were you using? If it was 1.28, that would > > explain what you saw. There was a fencepost error that could corrupt > > directories when it was optimizing/rehashing them. This bug was fixed > > in in the next version, which was rushed out the door as a result of > > this bug. Fortunately, 1.28 didn't get adopted by any distro's as far > > as I know > > Hmm. On a recently installed SuSE 8.1 machine: > > % rpm -qf `which e2fsck` > e2fsprogs-1.28-18 > > (maybe the -18 contains the fix?)
No, see below, I copied it from the SuSE security list.
>> This could be slightly off-topic, but isn't data corruption security >> related? >> SuSE 8.1 was delivered with e2fsprogs-1.28, which has a "fencepost >> error" (???) which could cause directory corruption. > > According to the maintainer of our e2fsprogs package, this referes to the > htree (hash tree) stuff in e2fsprogs which is *not* enabled in > SuSEs version of e2fsprogs. > > HTH > > best regards, > Rainer Link > (SuSE Labs)
--
GertJan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |