[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200828171107.GA32573@salvia>
Date: Fri, 28 Aug 2020 19:11:07 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Florian Westphal <fw@...len.de>
Cc: Will McVicker <willmcvicker@...gle.com>, stable@...r.kernel.org,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"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
On Fri, Aug 28, 2020 at 06:45:51PM +0200, Florian Westphal wrote:
> 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?
Oh, I overlook, existing kernels are affected. You're right.
> > > + if (l3num != NFPROTO_IPV4 && l3num != NFPROTO_IPV6)
> > > + return -EOPNOTSUPP;
>
> I vote to apply this to nf.git
I have rebased this patch on top of nf.git, attached what I'll apply
to nf.git.
View attachment "0001-netfilter-ctnetlink-add-a-range-check-for-l3-l4-prot.patch" of type "text/x-diff" (2167 bytes)
Powered by blists - more mailing lists