<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - nftables - dynamic update for verdict map from the packet path"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1736#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - nftables - dynamic update for verdict map from the packet path"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1736">bug 1736</a>
from <span class="vcard"><a class="email" href="mailto:dinhtrason@gmail.com" title="dinhtrason@gmail.com">dinhtrason@gmail.com</a>
</span></b>
<pre>(In reply to Pablo Neira Ayuso from <a href="show_bug.cgi?id=1736#c11">comment #11</a>)
<span class="quote">> This affinity map also needs to deal with two packets racing to set up the
> affinity?
>
> chain endpoint-1 {
> counter packets 2 bytes 224
> update @affinity-mappings { ip saddr : 11.0.2.2 } meta
> l4proto tcp dnat to 11.0.2.2 : 5001
> # lost race, re-lookup to use existing mapping
> meta l4proto tcp dnat to ip saddr map @affinity-mappings :
> 5001
> # not found, should not ever happen
> counter drop
> }</span >
I did not even think about the race condition. Thanks for highlighting this
special case.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>