linux-ext4 - Patches in the ext4 patch queue that should be marked for -stable

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>] [day] [month] [year] [list]

Date:	Mon, 05 Jan 2009 21:55:58 -0500
From:	"Theodore Ts'o" <tytso@....edu>
To:	linux-ext4@...r.kernel.org
Subject: Patches in the ext4 patch queue that should be marked for -stable


I believe the following patches should be destined for -stable kernel
tree in the ext4 patch queue.

Have I missed any patches?   Do you believe any of these patches
*shouldn't* be added to the stable kernel?

 * add-barrier-check-to-journal_wait_on_commit_record
 * aneesh-2-add-blocks-added-during-resize-to-bitmap
 * aneesh-3-use_EXT4_GROUP_INFO_NEED_INIT_BIT-during-resize
 * aneesh-7-dont-use-blocks-freed-but-not-yet-committed-in-buddy-cache-init
 * aneesh-8-fix-double-free-of-blocks
 * avoid-ext4-error-for-single-bg-fs
 * dont-overwrite-allocation_context-ac_status
 * ext4-Don-t-allow-new-groups-to-be-added-during-bloc.patch
 * ext4-Fix-s_dirty_blocks_counter-if-block-allocation.patch
 * ext4-Init-the-complete-page-while-building-buddy-ca.patch
 * ext4-Use-new-buffer_head-flag-to-check-uninit-group.patch
 * ext4-mark-the-blocks-inode-bitmap-beyond-end-of-gro.patch
 * fix-delalloc-writepages-to-allocate-at-correct-offset
 * fix-race-between-read_block_bitmap-and-mark_diskspace_used
 * fix-race-between-read_inode_bitmap-and-ext4_new_inode

					- Ted

--
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