From: NeilBrown <neilb@suse.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
tgraf@suug.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH] rhashtable: detect when object movement between tables might have invalidated a lookup
Date: Fri, 16 Nov 2018 17:59:19 +1100 [thread overview]
Message-ID: <878t1tece0.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181116055551.zxfydbpoicslsfkg@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
E
[-- Attachment #2.1: Type: text/plain, Size: 2011 bytes --]
On Fri, Nov 16 2018, Herbert Xu wrote:
> On Thu, Nov 15, 2018 at 10:32:13AM +1100, NeilBrown wrote:
>>
>> +#define RHT_NULLS_MARKER(ptr) \
>> + ((void *)NULLS_MARKER(((unsigned long) (ptr)) >> 1))
>> #define INIT_RHT_NULLS_HEAD(ptr) \
>> - ((ptr) = (typeof(ptr)) NULLS_MARKER(0))
>> + ((ptr) = RHT_NULLS_MARKER(&(ptr)))
>
> Why are you shifting this by one?
NULLS_MARKER assumes a hash value in which the bottom bits are most
likely to be unique. To convert this to a pointer which certainly not
valid, it shifts left by 1 and sets the lsb.
We aren't passing a hash value, but are passing an address instead.
In this case the bottom 2 bits are certain to be 0, and the top bit
could contain valuable information (on a 32bit system).
The best way to turn a pointer into a certainly-invalid pointer
is to just set the lsb. By shifting right by one, we discard an
uninteresting bit, preserve all the interesting bits, and effectively
just set the lsb.
I could add a comment explaining that if you like.
>
>> diff --git a/lib/rhashtable.c b/lib/rhashtable.c
>> index 30526afa8343..852ffa5160f1 100644
>> --- a/lib/rhashtable.c
>> +++ b/lib/rhashtable.c
>> @@ -1179,8 +1179,7 @@ struct rhash_head __rcu **rht_bucket_nested(const struct bucket_table *tbl,
>> unsigned int hash)
>> {
>> const unsigned int shift = PAGE_SHIFT - ilog2(sizeof(void *));
>> - static struct rhash_head __rcu *rhnull =
>> - (struct rhash_head __rcu *)NULLS_MARKER(0);
>> + static struct rhash_head __rcu *rhnull;
>
> I don't understand why you can't continue to do NULLS_MARKER(0) or
> RHT_NULLS_MARKER(0).
Because then the test
+ } while (he != RHT_NULLS_MARKER(head));
in __rhashtable_lookup() would always succeed, and it would loop
forever.
Thanks for the review.
NeilBrown
>
> Cheers,
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-11-16 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 23:32 [PATCH] rhashtable: detect when object movement between tables might have invalidated a lookup NeilBrown
2018-11-16 5:55 ` Herbert Xu
2018-11-16 6:59 ` NeilBrown [this message]
2018-11-19 3:54 ` Herbert Xu
2018-11-19 3:56 ` Herbert Xu
2018-11-19 4:06 ` Herbert Xu
2018-11-19 4:22 ` David Miller
2018-11-29 23:26 ` [PATCH v3] " NeilBrown
2018-12-01 8:47 ` Herbert Xu
2018-12-02 22:20 ` NeilBrown
2018-12-03 1:44 ` Herbert Xu
2018-12-03 22:28 ` [PATCH] " NeilBrown
2018-12-03 23:32 ` [PATCH v3] " David Miller
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=878t1tece0.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).