| 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
| ||
|
Message-Id: <20071002084143.110486039@mail.ustc.edu.cn> Date: Tue, 02 Oct 2007 16:41:43 +0800 From: Fengguang Wu <wfg@...l.ustc.edu.cn> To: Andrew Morton <akpm@...l.org> Cc: Michael Rubin <mrubin@...gle.com> Subject: [PATCH 0/5] sluggish writeback fixes Andrew, The following patches fix the sluggish writeback behavior. They are well understood and well tested - but not yet widely tested. The first patch reverts the debugging -mm only check_dirty_inode_list.patch - which is no longer necessary. The following 4 patches do the real jobs: [PATCH 2/5] writeback: fix time ordering of the per superblock inode lists 8 [PATCH 3/5] writeback: fix ntfs with sb_has_dirty_inodes() [PATCH 4/5] writeback: remove pages_skipped accounting in __block_write_full_page() [PATCH 5/5] writeback: introduce writeback_control.more_io to indicate more io They share the same goal as the following patches in -mm. Therefore I'd recommend to put the last 4 new ones after them: writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-2.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-3.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-4.patch writeback-fix-comment-use-helper-function.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-5.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-6.patch writeback-fix-time-ordering-of-the-per-superblock-dirty-inode-lists-7.patch writeback-fix-periodic-superblock-dirty-inode-flushing.patch Regards, Fengguang -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists