<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Trying to populate a set raises a netlink error "Could not process rule: No space left on device""
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1464#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Trying to populate a set raises a netlink error "Could not process rule: No space left on device""
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1464">bug 1464</a>
from <span class="vcard"><a class="email" href="mailto:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>(In reply to kfm from <a href="show_bug.cgi?id=1464#c6">comment #6</a>)
<span class="quote">> (In reply to Pablo Neira Ayuso from <a href="show_bug.cgi?id=1464#c5">comment #5</a>)
> > Is this easily reproducible in your testbed? I cannot reproduce it here yet.
> > I can see a fork() call in your nft-enoent binary. Could you attach the
> > strace -f output to track child process?
>
> Yes. Every time. I can reproduce it simply by applying the attached command
> stream directly with nft(8) so I'll attach a trace of that.</span >
I'm testing with 5.10.0-rc4+
so you there you do:
#1 Add this table
table ip raw {
set bogons {
type ipv4_addr
flags interval,timeout
timeout 4h5m
}
}
#2 then:
nft -f bug-1464-nft-input-stream.txt
#3 run again:
nft -f bug-1464-nft-input-stream.txt
and you hit the bug?
Maybe I'm overlooking something on the steps to reproduce this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>