From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, a.hajda@samsung.com
Subject: Re: [PATCH nf-next] netfilter: fix IS_ERR_VALUE usage
Date: Fri, 29 Apr 2016 11:30:10 +0200 [thread overview]
Message-ID: <20160429093010.GA14734@salvia> (raw)
In-Reply-To: <20160429091754.GN17538@breakpoint.cc>
On Fri, Apr 29, 2016 at 11:17:54AM +0200, Florian Westphal wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > This is a forward-ported original patch from Andrzej Hajda, he said:
> >
> > "IS_ERR_VALUE should be used only with unsigned long type.
> > Otherwise it can work incorrectly. To achieve this function
> > xt_percpu_counter_alloc is modified to return unsigned long,
> > and its result is assigned to temporary variable to perform
> > error checking, before assigning to .pcnt field.
> >
> > The patch follows conclusion from discussion on LKML [1][2].
> >
> > [1]: http://permalink.gmane.org/gmane.linux.kernel/2120927
> > [2]: http://permalink.gmane.org/gmane.linux.kernel/2150581"
> >
> > Original patch from Andrzej is here:
> >
> > http://patchwork.ozlabs.org/patch/582970/
> >
> > This patch has clashed with input validation fixes for x_tables.
>
> AFAICS this isn't a bug fix so I'm fine with this going into nf-next.
This seems to affect 32-bits arch, we could qualify this as nf. But
this has been there for a while without nobody noticing in runtime
kernels, this problem got uncovered by analysis I think.
prev parent reply other threads:[~2016-04-29 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 8:53 [PATCH nf-next] netfilter: fix IS_ERR_VALUE usage Pablo Neira Ayuso
2016-04-29 9:17 ` Florian Westphal
2016-04-29 9:30 ` Pablo Neira Ayuso [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=20160429093010.GA14734@salvia \
--to=pablo@netfilter.org \
--cc=a.hajda@samsung.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).