On Wed, 4 Feb 2009 21:00:13 -0500 Theodore Tso <tytso@xxxxxxx> wrote: > On Wed, Feb 04, 2009 at 11:58:33AM +0100, Rafael J. Wysocki wrote: > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12224 > > Subject : journal activity on inactive partition causes inactive harddrive spinup > > Submitter : C Sights <csights@xxxxxxxxxxx> > > Date : 2008-12-14 11:39 (53 days old) > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6 > > Handled-By : Eric Sandeen <sandeen@xxxxxxxxxx> > > Patches against ext3 have been posted by Jan Kara and have been sucked > into the mm tree. I don't know if Andrew is planning on waiting until > the next merge window, or is planning on pushing it sooner given that > it is a regression. Yes, I have jbd-fix-return-value-of-journal_start_commit.patch and revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch queued for 2.6.29. The secret algorithm for determining this is to peek in the series file (http://userweb.kernel.org/~akpm/mmotm/series) and see where I positioned the patch: # -> # more 2.6.29 queue: # # me: # migration-migrate_vmas-should-check-vma.patch rtc-update-maintainership-of-pxa-rtc-driver.patch lxfb-properly-alloc-cmap-in-all-cases-and-dont-leak-the-memory.patch gxfb-properly-alloc-cmap-and-plug-cmap-leak.patch gx1fb-properly-alloc-cmap-and-plug-cmap-leak.patch mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches.patch mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches-fix.patch -> jbd-fix-return-value-of-journal_start_commit.patch -> revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch writeback-fix-nr_to_write-counter.patch -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
