From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: Regression introduced by bfcfaa77bdf0f775263e906015982a608df01c76 (vfs: use 'unsigned long' accesses for dcache name comparison and hashing)
Date: Thu, 22 Mar 2012 17:41:57 -0400 [thread overview]
Message-ID: <20120322214157.GB12985@phenom.dumpdata.com> (raw)
In-Reply-To: <20120322203658.GC6589@ZenIV.linux.org.uk>
On Thu, Mar 22, 2012 at 08:36:58PM +0000, Al Viro wrote:
> On Thu, Mar 22, 2012 at 08:24:45PM +0000, Al Viro wrote:
> >
> > OK, full_name_hash()/hash_name() definitely have a mismatch and it's on the
> > names of length 8*n: trivial experiment shows that we have
> > name hash_name full_name_hash
> > a 61 61
> > ab 6261 6261
> > abc 636261 636261
> > abcd 64636261 64636261
> > abcdabc 64c6c4c2 64c6c4c2
> > abcdabcd efcead5 c8c6c4c2
> > abcdabcd9 efceb0e efceb0e
> >
> > Linus, which way do you prefer to shift it? Should hash_name() change to
> > match full_name_hash() or should it be the other way round?
> >
> > What happens is that you get multiplication by 9 and adding 0 in the former,
> > after having added the last full word. In the latter we add the last full
> > word, see that there's nothing left and bugger off.
>
> Guys, could you check if this fixes it?
Works for me! Thanks for coming up with a patch so quickly. Please add
Reported-and-Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thanks.
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 13e6a1f..7451d6f8 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -1439,10 +1439,10 @@ unsigned int full_name_hash(const unsigned char *name, unsigned int len)
>
> for (;;) {
> a = *(unsigned long *)name;
> - hash *= 9;
> if (len < sizeof(unsigned long))
> break;
> hash += a;
> + hash *= 9;
> name += sizeof(unsigned long);
> len -= sizeof(unsigned long);
> if (!len)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-03-22 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 18:38 Regression introduced by bfcfaa77bdf0f775263e906015982a608df01c76 (vfs: use 'unsigned long' accesses for dcache name comparison and hashing) Konrad Rzeszutek Wilk
2012-03-22 19:33 ` Eric Paris
2012-03-22 20:03 ` Eric Paris
2012-03-22 20:10 ` Al Viro
2012-03-22 20:09 ` Al Viro
2012-03-22 20:24 ` Al Viro
2012-03-22 20:36 ` Al Viro
2012-03-22 20:42 ` Linus Torvalds
2012-03-22 21:41 ` Konrad Rzeszutek Wilk [this message]
2012-03-22 21:54 ` Linus Torvalds
2012-03-22 21:59 ` Al Viro
2012-03-22 20:38 ` Linus Torvalds
2012-03-22 20:44 ` Al Viro
2012-03-22 20:52 ` Linus Torvalds
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=20120322214157.GB12985@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=xen-devel@lists.xensource.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