From: Theodore Ts'o <tytso@mit.edu>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>,
Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree
Date: Sun, 3 Feb 2013 09:57:42 -0500 [thread overview]
Message-ID: <20130203145742.GA5424@thunk.org> (raw)
In-Reply-To: <20130203081943.GF4937@mwanda>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Sun, Feb 03, 2013 at 11:19:43AM +0300, Dan Carpenter wrote:
>
> I don't get this warning on my version of Sparse.
>
> Sparse used to assume -m32 all the time but now that's been changed.
> Are you using the most recent version of Sparse? Try passing -m64.
Hmm, I got my version of sparse from
git://git.kernel.org/pub/scm/devel/sparse/sparse.git
... where the latest version is 0.4.4, dated November 21, 2011. Is
there a different dit repository I should be using?
I see that it doesn't complain with -m64, but the test program should
be valid for x86 with 32 bits just as much as 64 bits. Am I missing
something?
- Ted
[-- Attachment #2: testcase --]
[-- Type: text/plain, Size: 881 bytes --]
#!/bin/sh
cat > /tmp/testcase.c << EOF
#include <unistd.h>
#include <stdio.h>
struct rb_node {
unsigned long __rb_parent_color;
struct rb_node *rb_right;
struct rb_node *rb_left;
} __attribute__((aligned(sizeof(long))));
struct extent_status {
struct rb_node rb_node;
unsigned long es_lblk; /* first logical block extent covers */
unsigned long es_len; /* length of extent in block */
unsigned long long es_pblk : 62; /* first physical block */
unsigned long long es_status : 2; /* record the status of extent */
};
int main(int argc, char **argv)
{
struct extent_status es;
es.es_status = 3;
printf("%d\n", es.es_status);
printf("size %u\n", sizeof(es));
}
EOF
echo "sparse /tmp/testcase.c"
sparse /tmp/testcase.c
echo " "
echo "sparse -m32 /tmp/testcase.c"
sparse -m32 /tmp/testcase.c
echo " "
echo "sparse -m64 /tmp/testcase.c"
sparse -m64 /tmp/testcase.c
next prev parent reply other threads:[~2013-02-03 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:03 [PATCH 00/10 v3] ext4: extent status tree (step2) Zheng Liu
2013-01-23 12:03 ` [PATCH 01/10 v3] ext4: refine extent status tree Zheng Liu
2013-01-23 12:03 ` [PATCH 02/10 v3] ext4: remove EXT4_MAP_FROM_CLUSTER flag Zheng Liu
2013-01-23 12:03 ` [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree Zheng Liu
2013-01-29 3:03 ` Theodore Ts'o
2013-01-29 5:34 ` Zheng Liu
2013-01-29 17:28 ` Theodore Ts'o
2013-01-30 2:43 ` Zheng Liu
2013-02-03 3:03 ` Theodore Ts'o
2013-02-03 5:21 ` Zheng Liu
2013-02-03 8:19 ` Dan Carpenter
2013-02-03 14:57 ` Theodore Ts'o [this message]
2013-02-03 7:30 ` Sam Ravnborg
2013-01-23 12:03 ` [PATCH 04/10 v3] ext4: adjust interfaces of " Zheng Liu
2013-01-23 12:03 ` [PATCH 05/10 v3] ext4: track all extent status in " Zheng Liu
2013-01-23 12:03 ` [PATCH 06/10 v3] ext4: lookup block mapping " Zheng Liu
2013-01-23 12:03 ` [PATCH 07/10 v3] ext4: remove single extent cache Zheng Liu
2013-01-23 12:03 ` [PATCH 08/10 v3] fs: allow for fs-specific objects to be pruned as part of pruning inodes Zheng Liu
2013-01-23 12:03 ` [PATCH 09/10 v3] ext4: adjust some functions for reclaiming extents from extent status tree Zheng Liu
2013-01-23 12:04 ` [PATCH 10/10 v3] ext4: reclaim " Zheng Liu
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=20130203145742.GA5424@thunk.org \
--to=tytso@mit.edu \
--cc=dan.carpenter@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=wenqing.lz@taobao.com \
/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).