From: "Yan Zheng" <yanzheng@21cn.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [BUG?] "ext4_ext_put_in_cache" uses __u32 to receive physical block number.
Date: Fri, 27 Jul 2007 13:16:14 +0800 [thread overview]
Message-ID: <3d0408630707262216i3f8e1c35ub49be9c210f963d8@mail.gmail.com> (raw)
Hi, all
I think I found a bug in ext4/extents.c, "ext4_ext_put_in_cache" uses
"__u32" to receive physical block number. "ext4_ext_put_in_cache" is
used in "ext4_ext_get_blocks", it sets ext4 inode's extent cache
according most recently tree lookup (higher 16 bits of saved physical
block number are always zero). when serving a mapping request,
"ext4_ext_get_blocks" first check whether the logical block is in
inode's extent cache. if the logical block is in the cache and the
cached region isn't a gap, "ext4_ext_get_blocks" gets physical block
number by using cached region's physical block number and offset in
the cached region. as described above, "ext4_ext_get_blocks" may
return wrong result when there are physical block numbers bigger than
0xffffffff.
Regards
YZ
next reply other threads:[~2007-07-27 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 5:16 Yan Zheng [this message]
2007-07-27 15:39 ` [BUG?] "ext4_ext_put_in_cache" uses __u32 to receive physical block number Mingming Cao
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=3d0408630707262216i3f8e1c35ub49be9c210f963d8@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).