[Bug 1464] Trying to populate a set raises a netlink error "Could not process rule: No space left on device"

[bugzilla-daemon at netfilter.org]

https://bugzilla.netfilter.org/show_bug.cgi?id=1464

--- Comment #16 from Pablo Neira Ayuso <pablo at netfilter.org> ---
(In reply to kfm from comment #14)
> Created attachment 620 [details]
> bug-1464-strace-r2.txt
> 
> A fresh trace, having applied attachment #619 [details] (the
> NFT_MNL_ACK_MAXSIZE patch). The set was not yet cleared, so most - if not
> all - elements continue to overlap with the payload.

So after the patch, I can see it sends the netlink message:

sendmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000},
msg_namelen=12, msg_iov=[{iov_base=[{{len=20, type=NFNL_MSG_BATCH_BEGIN,
flags=NLM_F_REQUEST, seq=0, pid=0}, {nfgen_family=AF_UNSPEC,
version=NFNETLINK_V0, res_id=htons(2560)}, {{len=40,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_DELSETELEM, flags=NLM_F_REQUEST, seq=1,
pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0),
[{{nla_len=11, nla_type=0x2}, "\x62\x6f\x67\x6f\x6e\x73\x00"}, {{nla_len=8,
nla_type=NFNETLINK_V1}, "\x72\x61\x77\x00"}]}, {{len=51440,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_NEWSETELEM,
flags=NLM_F_REQUEST|NLM_F_CREATE, seq=2, pid=0}, {nfgen_family=AF_INET,
version=NFNETLINK_V0, res_id=htons(0), [{{nla_len=11, nla_type=0x2},
"\x62\x6f\x67\x6f\x6e\x73\x00"}, {{nla_len=8, nla_type=0x4},
"\x00\x00\x00\x1d"}, {{nla_len=8, nla_type=NFNETLINK_V1}, "\x72\x61\x77\x00"},
{{nla_len=51392, nla_type=NLA_F_NESTED|0x3},
"\x10\x00\x01\x80\x0c\x00\x01\x80\x08\x00\x01\x00\x00\x00\x00\x00\x18\x00\x02\x80\x08\x00\x03\x00\x00\x00\x00\x01\x0c\x00\x01\x80"...}]},
{{len=20, type=NFNL_MSG_BATCH_END, flags=NLM_F_REQUEST, seq=3, pid=0},
{nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(2560)}],
iov_len=51520}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 51520

I can see NFT_MSG_DELSETELEM (flush) coming before NFT_MSG_NEWSETELEM (add
elements) here above.

select(4, [3], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)                 
close(4)                                = 0                                     
close(3)                                = 0  

And kernel reports no error, nft does not print it either (strace does not show
any write() syscall)

I don't see any error in this trace at quick glance. Still issues on your side?

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20201202/f5bcc650/attachment-0001.html>