after reconsider, I think we can remove this check directly, since rht_grow_above_max() will be called to check the overflow again in rhashtable_insert_one.
and atomic_read(&table->hash.nelems) always compares with unsigned value, will force to switch unsigned, so the hash.nelems overflows can be accepted. -Rong
