From: "Kerin Millar" <kfm@plushkava.net>
To: "Pablo Neira Ayuso" <pablo@netfilter.org>, Slavko <linux@slavino.sk>
Cc: "netfilter ML" <netfilter@vger.kernel.org>
Subject: Re: Sets update
Date: Tue, 23 Jul 2024 12:32:50 +0100 [thread overview]
Message-ID: <205f7dcd-150c-42a7-83c0-6d4a36a5f2d5@app.fastmail.com> (raw)
In-Reply-To: <Zp96TJrXOz3ZIPLK@calendula>
On Tue, 23 Jul 2024, at 10:39 AM, Pablo Neira Ayuso wrote:
> On Tue, Jul 23, 2024 at 09:24:39AM +0200, Slavko wrote:
> [...]
>> (The host has >6 GB of free RAM, the list has ~1700 items)
>>
>> Initially i blame IP duplicates in downloaded list of IPs, but that was
>> unrelated to this error. When i remove the first "add" and "delete"
>> lines from script (thus just one "add"), it works. After initial fill it
>> works with all three commands (add+delete+add) on already filled set
>> and even when i flush that set, it still works. Only first fill (after
>> boot) ends with that error.
>>
>> When i delete and create that set, i got "Out of memory" again, the set
>> is defined as::
>>
>> table inet fw4 {
>> set myset {
>> type ipv4_addr
>> last counter
>> timeout 2d
>> }
>> }
>>
>> I tried to add "size" into it, but that doesn't help.
>>
>> I roughly remember, that i read something about some memory limit in
>> container (i am not in container), but i am not able to find that
>> again to check if that is problem.
>>
>> Please, what can cause that initial fill error, how i can debug/solve
>> it?
>
> Kernel is likely missing this patch:
>
> commit fa23e0d4b756d25829e124d6b670a4c6bbd4bf7e
> Author: Florian Westphal <fw@strlen.de>
> Date: Wed May 8 14:52:47 2024 +0200
>
> netfilter: nf_tables: allow clone callbacks to sleep
Would it be safe to backport the following two commits to linux-6.6.y in isolation?
3c13725f43dcf43ad8a9bcd6a9f12add19a8f93e (bail out if stateful expression provides no .clone)
fa23e0d4b756d25829e124d6b670a4c6bbd4bf7e (allow clone callbacks to sleep)
--
Kerin Millar
next prev parent reply other threads:[~2024-07-23 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 7:44 Sets update Slavko
2024-07-21 9:58 ` Kerin Millar
2024-07-21 10:04 ` Kerin Millar
2024-07-21 11:23 ` Slavko
2024-07-21 12:29 ` Kerin Millar
2024-07-21 14:38 ` Slavko
2024-07-21 15:46 ` Kerin Millar
2024-07-23 7:24 ` Slavko
2024-07-23 7:37 ` Slavko
2024-07-23 9:39 ` Pablo Neira Ayuso
2024-07-23 10:23 ` Slavko
2024-07-23 11:32 ` Kerin Millar [this message]
2024-07-23 12:19 ` Pablo Neira Ayuso
2024-07-21 16:09 ` Eric
2024-07-21 16:46 ` Kerin Millar
2024-07-21 17:58 ` Slavko
2024-07-22 20:36 ` Pablo Neira Ayuso
2024-07-23 7:26 ` Slavko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=205f7dcd-150c-42a7-83c0-6d4a36a5f2d5@app.fastmail.com \
--to=kfm@plushkava.net \
--cc=linux@slavino.sk \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox