On Wed, Jul 29, 2009 at 10:42:09AM +0100, Daniel J Blueman wrote: > When mounting a btrfs filesystem on my server running 2.6.31-rc4, > kmemcheck spotted some believed-uninitialised memory [1] 128 bytes > into the inode structure access from BTRFS_I [2,3]. > > The filesystem was created with btrfstools-0.18 under 2.6.30 - perhaps > an issue relating to the forward rolling disk format changes - or > simply relating to the inode size? Should > be reproducible.
Ok, this is coming from the RB_CLEAR_NODE() call, which reads the current value of the parent pointer. I'll fix it up, thanks for sending the bug report along. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
