From: Eric Sandeen <sandeen@redhat.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Mingming Cao <cmm@us.ibm.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix build failure if DX_DEBUG
Date: Wed, 11 Jun 2008 11:03:39 -0500 [thread overview]
Message-ID: <484FF75B.8090403@redhat.com> (raw)
In-Reply-To: <484F9030.2020800@cn.fujitsu.com>
Li Zefan wrote:
> I got build failure when I turned on DX_DEBUG.
>
> fs/ext4/namei.c: In function ‘dx_show_leaf’:
> fs/ext4/namei.c:291: error: implicit declaration of function ‘ext4_next_entry’
> fs/ext4/namei.c:291: warning: assignment makes pointer from integer without a cast
>
> Move the definition of ext4_next_entry() upwards just as ext3 code.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Thanks, I added this to the bugfix portion of the ext4 patch queue.
-Eric
> ---
> fs/ext4/namei.c | 19 ++++++++++---------
> 1 files changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index ab16bea..4315fd7 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -183,6 +183,16 @@ static int ext4_dx_add_entry(handle_t *handle, struct dentry *dentry,
> struct inode *inode);
>
> /*
> + * p is at least 6 bytes before the end of page
> + */
> +static inline struct ext4_dir_entry_2 *
> +ext4_next_entry(struct ext4_dir_entry_2 *p)
> +{
> + return (struct ext4_dir_entry_2 *)((char *)p +
> + ext4_rec_len_from_disk(p->rec_len));
> +}
> +
> +/*
> * Future: use high four bits of block for coalesce-on-delete flags
> * Mask them off for now.
> */
> @@ -554,15 +564,6 @@ static int ext4_htree_next_block(struct inode *dir, __u32 hash,
>
>
> /*
> - * p is at least 6 bytes before the end of page
> - */
> -static inline struct ext4_dir_entry_2 *ext4_next_entry(struct ext4_dir_entry_2 *p)
> -{
> - return (struct ext4_dir_entry_2 *)((char *)p +
> - ext4_rec_len_from_disk(p->rec_len));
> -}
> -
> -/*
> * This function fills a red-black tree with information from a
> * directory block. It returns the number directory entries loaded
> * into the tree. If there is an error it is returned in err.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-11 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 8:43 [PATCH] ext4: fix build failure if DX_DEBUG Li Zefan
2008-06-11 16:03 ` Eric Sandeen [this message]
2008-07-06 4:07 ` Theodore Tso
2008-07-06 4:10 ` Eric Sandeen
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=484FF75B.8090403@redhat.com \
--to=sandeen@redhat.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=tytso@mit.edu \
/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).