Greg KH wrote: > On Mon, Nov 10, 2008 at 10:42:20AM +0800, Eugene Teo wrote: >> Greg KH wrote: >> >> Please change the description of the bug to: >> >> "A very large directory with many read failures (either due to storage >> problems, or due to invalid size & blocks from corruption) will generate >> a printk storm as the filesystem continues to try to read all the >> blocks. This flood of messages can tie up the box until it is complete - >> which may be a very long time, especially for very large corrupted values. >> >> This is fixed by only reporting the corruption once each time we try to >> read the directory." >> >> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commitdiff;h=bd39597 > > Hm, why would I change the description to be different from what the > developer asked it to be? It references the specific changeset you > point to above already. I'm inclined to stick with the text that the > developer asked to be used (especially as this is a combined 3 > changesets into one patch). There were 3 changesets upstream, one for each fs; I copied the changelog from the ext4 changeset because it's the patch that I originally authored, and combined it with the ext2 & ext3 changes as well. The upstream ext4 changelog happened to contain some color commentary from Ted; the ext2 & ext3 changelogs did not. I don't really give a damn what the stable changelog says, and personally my feelings won't be hurt with either text, I'll just be happy to have the bug fixed in -stable. Thanks, -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
