From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: linux-nfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Fan Yong <yong.fan@whamcloud.com>,
bfields@redhat.com, sandeen@redhat.com,
Andreas Dilger <adilger@whamcloud.com>
Subject: Re: [PATCH 5 2/4] Return 32/64-bit dir name hash according to usage type
Date: Tue, 06 Mar 2012 01:40:05 +0100 [thread overview]
Message-ID: <4F555CE5.7050401@itwm.fraunhofer.de> (raw)
In-Reply-To: <20120305155939.GE21356@thunk.org>
On 03/05/2012 04:59 PM, Ted Ts'o wrote:
> On Mon, Jan 09, 2012 at 02:21:48PM +0100, Bernd Schubert wrote:
>> diff --git a/fs/ext4/hash.c b/fs/ext4/hash.c
>> index ac8f168..fa8e491 100644
>> --- a/fs/ext4/hash.c
>> +++ b/fs/ext4/hash.c
>> @@ -200,8 +200,8 @@ int ext4fs_dirhash(const char *name, int len, struct dx_hash_info *hinfo)
>> return -1;
>> }
>> hash = hash& ~1;
>> - if (hash == (EXT4_HTREE_EOF<< 1))
>> - hash = (EXT4_HTREE_EOF-1)<< 1;
>> + if (hash == (EXT4_HTREE_EOF_32BIT<< 1))
>> + hash = (EXT4_HTREE_EOF_32BIT - 1)<< 1;
>> hinfo->hash = hash;
>> hinfo->minor_hash = minor_hash;
>> return 0;
>
> Is there a reason why we don't need to avoid the collsion with the
> 64-bit EOF value as well? i.e., I think we also need to add:
>
> if (hash == (EXT4_HTREE_EOF_64BIT<< 1))
> hash = (EXT4_HTREE_EOF_64BIT - 1)<< 1;
>
> - Ted
Thanks for looking into it, really appreciated!
Yeah, you are right, we also should check for 64-bit EOF. But wouldn't
be something like this be better?
/* check for hash collision */
if(is_32bit_api() ) {
if (hash == (EXT4_HTREE_EOF_32BIT<< 1))
hash = (EXT4_HTREE_EOF_32BIT - 1)<< 1;
} else {
if (hash == (EXT4_HTREE_EOF_64BIT<< 1))
hash = (EXT4_HTREE_EOF_64BIT - 1)<< 1;
}
Or am I over engineering?
Thanks,
Bernd
next prev parent reply other threads:[~2012-03-06 0:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 13:21 [PATCH 0/4] [RESEND] 32/64 bit llseek hashes (v5) Bernd Schubert
2012-01-09 13:21 ` [PATCH 5 1/4] Add new FMODE flags: FMODE_32bithash and FMODE_64bithash Bernd Schubert
2012-01-09 13:21 ` [PATCH 5 2/4] Return 32/64-bit dir name hash according to usage type Bernd Schubert
2012-03-05 15:59 ` Ted Ts'o
2012-03-06 0:40 ` Bernd Schubert [this message]
2012-03-06 2:28 ` Ted Ts'o
2012-03-06 9:59 ` Bernd Schubert
2012-03-06 15:15 ` Ted Ts'o
2012-03-07 9:01 ` Bernd Schubert
2012-04-20 20:04 ` Eric Sandeen
2012-04-22 12:51 ` Bernd Schubert
2012-04-23 20:37 ` Eric Sandeen
2012-04-23 20:52 ` Bernd Schubert
2012-04-23 21:22 ` Eric Sandeen
2012-04-23 22:23 ` Eric Sandeen
2012-04-23 22:42 ` Andreas Dilger
2012-04-24 16:10 ` Bernd Schubert
2012-01-09 13:21 ` [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() Bernd Schubert
2012-03-06 0:08 ` Ted Ts'o
2012-03-06 2:08 ` J. Bruce Fields
2012-03-06 15:18 ` Ted Ts'o
2012-03-06 15:28 ` J. Bruce Fields
2012-03-09 20:51 ` Ted Ts'o
2012-03-12 15:09 ` Ted Ts'o
2012-03-12 15:49 ` J. Bruce Fields
2012-03-12 22:22 ` J. Bruce Fields
2012-03-13 20:01 ` J. Bruce Fields
2012-03-13 20:03 ` Bernd Schubert
2012-03-13 20:34 ` J. Bruce Fields
2012-03-13 21:09 ` Bernd Schubert
2012-03-13 21:29 ` J. Bruce Fields
2012-03-14 14:32 ` Bernd Schubert
2012-03-14 16:05 ` J. Bruce Fields
2012-03-16 21:22 ` Bernd Schubert
2012-03-19 2:54 ` Ted Ts'o
2012-03-19 20:00 ` J. Bruce Fields
2012-03-20 0:10 ` Ted Ts'o
2012-04-12 20:49 ` J. Bruce Fields
2012-04-12 21:22 ` Bernd Schubert
2012-04-12 21:25 ` J. Bruce Fields
2012-03-13 21:10 ` Ted Ts'o
2012-03-13 21:27 ` J. Bruce Fields
2012-01-09 13:21 ` [PATCH 5 4/4] nfsd: vfs_llseek() with 32 or 64 bit offsets (hashes) Bernd Schubert
2012-01-10 11:27 ` [PATCH 0/4] [RESEND] 32/64 bit llseek hashes (v5) Andreas Dilger
2012-01-11 14:48 ` J. Bruce Fields
2012-01-11 15:31 ` Ted Ts'o
2012-03-05 12:23 ` Bernd Schubert
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=4F555CE5.7050401@itwm.fraunhofer.de \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=adilger@whamcloud.com \
--cc=bfields@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
--cc=yong.fan@whamcloud.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).