linux-ext4 - Re: Ext4 patch queue updated(2.6.23-rc6)

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]

Message-ID: <20070914225438.GK5377@schatzie.adilger.int>
Date:	Fri, 14 Sep 2007 16:54:38 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Mingming Cao <cmm@...ibm.com>
Cc:	Valerie Clement <valerie.clement@...l.net>,
	linux-ext4 <linux-ext4@...r.kernel.org>, tytso@....edu
Subject: Re: Ext4 patch queue updated(2.6.23-rc6)

On Sep 14, 2007  12:03 -0700, Mingming Cao wrote:
> Ted, could you please update the ext4 git tree with the patches before
> the "unstable" mark, so we could get more air time in mm tree for
> testing?
> 
> Thanks,
> Mingming
> 
> current patch series
> 
> # Rebased the patches to 2.6.23-rc6
> jbd_slab_cleanup.patch
> sparse-fix.patch
> 
> # Add journal checksums
> ext4-journal_chksum-2.6.20.patch
> ext4-journal-chksum-review-fix.patch

Actually, the journal checksum patches should probably be moved into
the "unstable" part of the series, given the number of problems reported
on them (also in more heavy testing at CFS).  These are also not in use
in production anywhere, unlike e.g. uninit_groups which have 6 months *
50 servers of testing or more.

> #########
> #FLEX_BG
> ########
> flex_bg_kernel.patch

This should probably go into the "stable" part of the patches - it
is a conceptually simple patch, and the sooner INCOMPAT_FLEX_BG gets
upstream the better.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
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