On Tue, Sep 06, 2016 at 10:33:37PM +0800, Liping Zhang wrote: > From: Liping Zhang <liping.zhang@xxxxxxxxxxxxxx> > > Although the validation of queues_total and queuenum is checked in nft > utility, but user can add nft rules via nfnetlink, so it is necessary > to check the validation at the nft_queue expr init routine too. Applied, thanks. More comments on things I see on nft_queue at this stage: 1) Another issue, I can see nfqueue_hash() depends on CONFIG_IP6_NF_IPTABLES, this is not good since nft_queue infrastructure should not depend on iptables. Probably making this dependent of CONFIG_IPV6 is enough, unless you find anything better. 2) It would be good if nft_queue takes a _SREG_FROM and _SREG_TO to select the queue numbers, in a similar fashion to nft_nat. The idea is that we allow plugging nft_queue into nftables mapping, currently this is not working given that the queue number is passed as an attribute that contains the value. 3) It would be good to add py tests with larger range. I remember that the range 1-65535 currently doesn't work in both nft_queue and xt_NFQUEUE because the queue_total arithmetics are not right. It would be great if you can have a look into this. Thanks! -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
