linux-ext4 - Re: fsck errors encountered when applying patch "ext4: fix BUG when calling ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Feb 2009 17:37:35 -0800
From:	Michael Rubin <mrubin@...gle.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Xiang Wang <xiangw@...gle.com>, linux-ext4@...r.kernel.org,
	aneesh.kumar@...ux.vnet.ibm.com,
	Curt Wohlgemuth <curtw@...gle.com>,
	Chad Talbott <ctalbott@...gle.com>,
	Frank Mayhar <fmayhar@...gle.com>
Subject: Re: fsck errors encountered when applying patch "ext4: fix BUG when 
	calling ext4_error with locked block group"

On Fri, Feb 20, 2009 at 5:29 PM, Theodore Tso <tytso@....edu> wrote:
> One of the downsides of trying to backport a lot of changes to a
> kernel version as old as 2.6.26 is that you miss changes like this.
> You might want to think about leapfrogging to a newer kernel at some
> point....

We know. Our qualifying process is not the most light weight and the
kernel moves fast. Normally we take a snapshot and qualify it, trying
to take upstream patches when we can and then also publishing bugs we
find. The problem is that with ext4 still undergoing active dev we
want to be able to keep our ext4 portion of the tree as up to date as
possible.

I admit it's a bit of a balancing act.

Hopefully we won't be causing a lot of undue burden on this list.

Thanks for this.

Michael Rubin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html