From: Chris Mason <chris.mason@oracle.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [2.6.31-rc4] uninitialised memory during read_sb...
Date: Wed, 29 Jul 2009 09:03:07 -0400 [thread overview]
Message-ID: <20090729130307.GG13940@think> (raw)
In-Reply-To: <6278d2220907290242p1d8bb168g818e4e517847ad5f@mail.gmail.com>
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
prev parent reply other threads:[~2009-07-29 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 22:05 [2.6.31-rc4] uninitialised memory during read_sb Daniel J Blueman
2009-07-29 9:42 ` Daniel J Blueman
2009-07-29 13:03 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090729130307.GG13940@think \
--to=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox