<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - nft_set_hash fast lookup broken for 2 byte keys"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1199#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - nft_set_hash fast lookup broken for 2 byte keys"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1199">bug 1199</a>
from <span class="vcard"><a class="email" href="mailto:makovick@gmail.com" title="Jindřich Makovička <makovick@gmail.com>"> <span class="fn">Jindřich Makovička</span></a>
</span></b>
<pre>When searching for this bug, I also found this piece of code in
nft_hash_deactivate():
hlist_for_each_entry(he, &priv->table[hash], node) {
if (!memcmp(nft_set_ext_key(&this->ext), &elem->key.val,
set->klen) ||
nft_set_elem_active(&he->ext, genmask)) {
nft_set_elem_change_active(net, set, &he->ext);
return he;
}
}
The logical OR looks fishy to me. Shouldn't be && there instead?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>