linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FNST-Wang Chen <wangchen@cn.fujitsu.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Wang Chen <ellre923@gmail.com>, linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext3: Fix not initialized hash info in ext3_dx_find_entry()
Date: Fri, 31 Aug 2007 09:34:39 +0800	[thread overview]
Message-ID: <46D7702F.6000607@cn.fujitsu.com> (raw)
In-Reply-To: <20070830152949.GE10160@thunk.org>

Agree, thanks.

Theodore Tso said the following on 2007-8-30 23:29:
> On Thu, Aug 30, 2007 at 10:42:33PM +0800, Wang Chen wrote:
>   
>> +               if (dentry){
>> +                       ext3fs_dirhash(dentry->d_name.name, 
>> dentry->d_name.len,
>> +                                      &hinfo);
>> +               } else {
>> +                       return NULL;
>> +               }
>>     
>
> It's really not necessary to call ext3fs_dirhash(), since we don't
> need the hash value for the '.' and '..' case.  So here's a better
> patch....
>
>      	      	    	    	- Ted
>
> >From c2ff518e6f529f1d8b627f0e8be5d6f8af32747f Mon Sep 17 00:00:00 2001
> From: Theodore Ts'o <tytso@mit.edu>
> Date: Thu, 30 Aug 2007 11:26:24 -0400
> Subject: [PATCH] ext3: Fix use of uninitialized variable in ext3_dx_find_entry()
>
> In the case where we are looking up '.' and '..', those files are
> always in the first directory block, so we don't need worry about the
> hash value.  This avoids a lint warning message, as a minor cleanup.
>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
>  fs/ext3/namei.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext3/namei.c b/fs/ext3/namei.c
> index 1586807..c278fc7 100644
> --- a/fs/ext3/namei.c
> +++ b/fs/ext3/namei.c
> @@ -932,7 +932,7 @@ static struct buffer_head * ext3_dx_find_entry(struct dentry *dentry,
>  {
>  	struct super_block * sb;
>  	struct dx_hash_info	hinfo;
> -	u32 hash;
> +	u32 hash = 0;
>  	struct dx_frame frames[2], *frame;
>  	struct ext3_dir_entry_2 *de, *top;
>  	struct buffer_head *bh;
> @@ -947,13 +947,13 @@ static struct buffer_head * ext3_dx_find_entry(struct dentry *dentry,
>  	if (namelen > 2 || name[0] != '.'||(name[1] != '.' && name[1] != '\0')){
>  		if (!(frame = dx_probe(dentry, NULL, &hinfo, frames, err)))
>  			return NULL;
> +		hash = hinfo.hash;
>  	} else {
>  		frame = frames;
>  		frame->bh = NULL;			/* for dx_release() */
>  		frame->at = (struct dx_entry *)frames;	/* hack for zero entry*/
>  		dx_set_block(frame->at, 0);		/* dx_root block is 0 */
>  	}
> -	hash = hinfo.hash;
>  	do {
>  		block = dx_get_block(frame->at);
>  		if (!(bh = ext3_bread (NULL,dir, block, 0, err)))
>   


-- 
Best Regards,
A new email address of FJWAN is launched from Apr.1 2007.
The updated address is: wangchen@cn.fujitsu.com
--------------------------------------------------
Wang Chen
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
TEL:+86+25-86630566-850
FUJITSU INTERNAL:79955-850
FAX:+86+25-83317685
MAIL:wangchen@cn.fujitsu.com
--------------------------------------------------

      reply	other threads:[~2007-08-31  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 14:42 [PATCH] ext3: Fix not initialized hash info in ext3_dx_find_entry() Wang Chen
2007-08-30 15:29 ` Theodore Tso
2007-08-31  1:34   ` FNST-Wang Chen [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=46D7702F.6000607@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=ellre923@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --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).