Arturo Borrero Gonzalez <arturo@xxxxxxxxxxxxx> wrote: > In the current setup, nft (the frontend object) is using the xzalloc() function > from libnftables, which does not makes sense, as this is typically an internal > helper function. > > In order to don't use this public libnftables symbol (a later patch just > removes it), let's introduce a new allocation function in the nft frontend. > This results in a bit of code duplication, but given the simplicity of the code, > I don't think it's a big deal. > > Other possible approach would be to have xzalloc() become part of libnftables > public API, but that is a much worse scenario I think. Agree, thus: Acked-by: Florian Westphal <fw@xxxxxxxxx>
