[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200828164551.GG7319@breakpoint.cc>
Date: Fri, 28 Aug 2020 18:45:51 +0200
From: Florian Westphal <fw@...len.de>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: Will McVicker <willmcvicker@...gle.com>, stable@...r.kernel.org,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
Florian Westphal <fw@...len.de>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH v3 1/1] netfilter: nat: add a range check for l3/l4
protonum
Pablo Neira Ayuso <pablo@...filter.org> wrote:
> Hi Will,
>
> Given this is for -stable maintainers only, I'd suggest:
>
> 1) Specify what -stable kernel versions this patch applies to.
> Explain that this problem is gone since what kernel version.
>
> 2) Maybe clarify that this is only for stable in the patch subject,
> e.g. [PATCH -stable v3] netfilter: nat: add a range check for l3/l4
Hmm, we silently accept a tuple that we can't really deal with, no?
> > + if (l3num != NFPROTO_IPV4 && l3num != NFPROTO_IPV6)
> > + return -EOPNOTSUPP;
I vote to apply this to nf.git
Powered by blists - more mailing lists