On 30 Sep 2024, at 22:50, Paolo Valerio wrote: > The ovs_scan() doesn't enforce in-range values and so > lsbits are stored in case of out-of-range or negative values. > > This way negative or values greater than MAX_UINT32 for "default" are > all accepted in dpctl_ct_set_limits(), but they will eventually be > casted to uint32_t, whereas for zones all the values above are > considered invalid. > > Align their behaviors and extend the tests for checking values out of > the range. > > Signed-off-by: Paolo Valerio <[email protected]> Recheck-request: github-robot _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
- [ovs-dev] [PATCH v2 1/6] conntrack: Correctly annotate conn... Paolo Valerio
- [ovs-dev] [PATCH v2 2/6] conntrack: Add zone limit cov... Paolo Valerio
- [ovs-dev] [PATCH v2 3/6] conntrack: Do not use atomics... Paolo Valerio
- [ovs-dev] [PATCH v2 6/6] dpctl: Do not allow out of ra... Paolo Valerio
- Re: [ovs-dev] [PATCH v2 6/6] dpctl: Do not allow o... Eelco Chaudron
- [ovs-dev] [PATCH v2 5/6] conntrack: Use a per zone def... Paolo Valerio
- [ovs-dev] [PATCH v2 4/6] conntrack: Turn zl local limi... Paolo Valerio
- Re: [ovs-dev] [PATCH v2 1/6] conntrack: Correctly anno... Aaron Conole
- Re: [ovs-dev] [PATCH v2 1/6] conntrack: Correctly anno... Aaron Conole
- Re: [ovs-dev] [PATCH v2 1/6] conntrack: Correctly ... Ilya Maximets
- Re: [ovs-dev] [PATCH v2 1/6] conntrack: Correc... Aaron Conole
