[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171204101340.GA7871@salvia>
Date: Mon, 4 Dec 2017 11:13:40 +0100
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Linus Lüssing <linus.luessing@...3.blue>
Cc: netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
Florian Westphal <fw@...len.de>, linux-kernel@...r.kernel.org,
coreteam@...filter.org, netfilter-devel@...r.kernel.org,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"David S . Miller" <davem@...emloft.net>
Subject: Re: [Bridge] [PATCH net-next] bridge: ebtables: Avoid resetting
limit rule state
On Mon, Dec 04, 2017 at 06:20:06AM +0100, Linus Lüssing wrote:
> On Mon, Dec 04, 2017 at 05:53:35AM +0100, Linus Lüssing wrote:
> > And so, no I do not have this patch. I looked at it now, but it
> > does not seem to have any relation with .matchinfo, does it?
>
> Relation between .usersize and .checkentry I ment, not
> .usersize and .matchinfo.
In your patch, info->prev comes set to a value from userspace, right?
commit 324318f0248c31be8a08984146e7e4dd7cdd091d
Author: Willem de Bruijn <willemb@...gle.com>
Date: Tue May 9 16:17:37 2017 -0400
netfilter: xtables: zero padding in data_to_user
Since that patch above, the data area is zero'ed before dumped to
userspace, so we would get a null info->prev, hence defeating the
trick your patch relies on.
Am I missing anything?
Powered by blists - more mailing lists