On Friday 2018-04-20 10:47, Pablo Neira Ayuso wrote:
>> - if ((event != NFT_MSG_DELRULE) && (rule->list.prev != &chain->rules)) {
>> - prule = list_prev_entry(rule, list);
>> - if (nla_put_be64(skb, NFTA_RULE_POSITION,
>> - cpu_to_be64(prule->handle),
>> + if ((event != NFT_MSG_DELRULE)) {
>> + int pos = rule_get_position(rule, &chain->rules);
>> +
>> + if (nla_put_be64(skb, NFTA_RULE_POSITION, cpu_to_be64(pos),
>
>Rule counting to locate rule position is prone to races, the use of the
>handle to identify the position to replace rules help us make sure that
>we replace the right rule with several concurrent nft.
That is absolutely understandable, but then the handle, which I take works like
a uuid or an sql auto_increment, should be sent with a "handle" label, and not
be advertised as a "position" or" index" IMO, since these two sort of convey a
hole-free sequence.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
