From: Florian Westphal <fw@strlen.de>
To: "Julius Rüberg" <julius.rueberg@student.kit.edu>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables set/map operations failing in user namespace with Linux 7.1.6
Date: Mon, 10 Aug 2026 03:53:31 +0200 [thread overview]
Message-ID: <ankvG2B0B35KbGen@strlen.de> (raw)
In-Reply-To: <582d218b638be68342dd80893c41746b35c1be76.camel@student.kit.edu>
Julius Rüberg <julius.rueberg@student.kit.edu> wrote:
> I'm reaching out because I'm encountering an issue with nftables using set/map
> operations (e.g., ip6 daddr set ip6 daddr map @forwardmap) inside user namespaces,
> introduced somewhere between Linux 7.0.12 and 7.1.3.
> I don't encounter the issue on the LTS Kernel (6.18.43).
>
> If this is now intentionally restricted,
Yes:
commit 968cc2c96390f06e56ed6a43f935bfebdefed28f
Author: Florian Westphal <fw@strlen.de>
Date: Sat May 16 23:23:21 2026 +0800
netfilter: disable payload mangling in userns
We should be able to lift that restriction in the coming weeks,
after stricter offset/length validation is in place.
prev parent reply other threads:[~2026-08-10 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 1:17 nftables set/map operations failing in user namespace with Linux 7.1.6 Julius Rüberg
2026-08-10 1:53 ` Florian Westphal [this message]
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=ankvG2B0B35KbGen@strlen.de \
--to=fw@strlen.de \
--cc=julius.rueberg@student.kit.edu \
--cc=netfilter@vger.kernel.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