From: Jakub Kicinski <kuba@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Eric Dumazet <edumazet@google.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>, Thomas Graf <tgraf@suug.ch>,
Laura Garcia Liebana <nevola@gmail.com>,
John Fastabend <john.fastabend@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH nf-next v4 1/5] net: sched: Micro-optimize egress handling
Date: Mon, 25 Jan 2021 11:39:08 -0800 [thread overview]
Message-ID: <20210125113908.6951b6f8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210124103301.GA1056@wunner.de>
On Sun, 24 Jan 2021 11:33:01 +0100 Lukas Wunner wrote:
> On Fri, Jan 22, 2021 at 10:40:05AM +0100, Eric Dumazet wrote:
> > On Fri, Jan 22, 2021 at 9:55 AM Lukas Wunner <lukas@wunner.de> wrote:
> > > sch_handle_egress() returns either the skb or NULL to signal to its
> > > caller __dev_queue_xmit() whether a packet should continue to be
> > > processed.
> > >
> > > The skb is always non-NULL, otherwise __dev_queue_xmit() would hit a
> > > NULL pointer deref right at its top.
> > >
> > > But the compiler doesn't know that. So if sch_handle_egress() signals
> > > success by returning the skb, the "if (!skb) goto out;" statement
> > > results in a gratuitous NULL pointer check in the Assembler output.
> > >
> > > Avoid by telling the compiler that __dev_queue_xmit() is never passed a
> > > NULL skb.
> [...]
> > > we're about to add a netfilter egress hook to __dev_queue_xmit()
> > > and without the micro-optimization, it will result in a performance
> > > degradation which is indeed measurable:
> [...]
> > > --- a/net/core/dev.c
> > > +++ b/net/core/dev.c
> > > +__attribute__((nonnull(1)))
> > > static int __dev_queue_xmit(struct sk_buff *skb, struct net_device *sb_dev)
> > > {
> > > struct net_device *dev = skb->dev;
> >
> > It is a bit sad the compilers do not automatically get this knowledge
> > from the very first instruction :
> >
> > struct net_device *dev = skb->dev;
>
> The compiler (gcc) is capable of doing that, but the feature was disabled by:
>
> commit a3ca86aea507904148870946d599e07a340b39bf
> Author: Eugene Teo <eteo@redhat.com>
> Date: Wed Jul 15 14:59:10 2009 +0800
>
> Add '-fno-delete-null-pointer-checks' to gcc CFLAGS
>
> If -fno-delete-null-pointer-checks is dropped from the top-level Makefile
> then the gratuitous NULL pointer checks disappear from the Assembler output,
> obviating the need to litter hot paths with __attribute__((nonnull(1)))
> annotations.
>
> Taking a closer look at that commit, its rationale appears questionable:
> It says that broken code such as ...
>
> struct agnx_priv *priv = dev->priv;
>
> if (!dev)
> return;
>
> ... would result in the NULL pointer check being optimized away.
> The commit message claims that keeping the NULL pointer check in
> "makes it harder to abuse" the broken code.
>
> I don't see how that's the case: If dev is NULL, the NULL pointer
> dereference at the function's top causes termination of the task
> in kernel/exit.c:do_exit(). So the NULL pointer check is never
> reached by the task. If on the other hand dev is non-NULL,
> the task isn't terminated but then the NULL pointer check is
> unnecessary as well.
>
> So the point of the commit remains elusive to me. I could submit
> an RFC patch which drops -fno-delete-null-pointer-checks and see
> if any security folks cry foul. Thoughts?
I wonder if modern compilers can't simply warn about this particular
case. Not to mention our static checkers..
Dan, do you think the concern from the above-quoted commit is still
valid? Is this something that smatch flags these days? We're apparently
paying a real performance price in networking for tying compiler's hands
with -fno-delete-null-pointer-checks
next prev parent reply other threads:[~2021-01-26 1:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:47 [PATCH nf-next v4 0/5] Netfilter egress hook Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 1/5] net: sched: Micro-optimize egress handling Lukas Wunner
2021-01-22 9:40 ` Eric Dumazet
2021-01-24 10:33 ` Lukas Wunner
2021-01-25 19:39 ` Jakub Kicinski [this message]
2021-01-26 8:58 ` Dan Carpenter
2021-01-30 16:00 ` Lukas Wunner
2021-01-24 3:26 ` Jakub Kicinski
2021-01-24 10:46 ` Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 2/5] netfilter: Rename ingress hook include file Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 3/5] netfilter: Generalize " Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 4/5] netfilter: Introduce egress hook Lukas Wunner
2021-01-26 19:13 ` Daniel Borkmann
2021-09-11 21:26 ` Lukas Wunner
2021-09-15 9:45 ` Daniel Borkmann
2021-01-22 8:47 ` [PATCH nf-next v4 5/5] af_packet: " Lukas Wunner
2021-01-22 16:13 ` Willem de Bruijn
2021-01-24 11:14 ` Lukas Wunner
2021-01-24 16:18 ` Willem de Bruijn
2021-01-30 16:26 ` Lukas Wunner
2021-01-30 16:58 ` Willem de Bruijn
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=20210125113908.6951b6f8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=coreteam@netfilter.org \
--cc=dan.carpenter@oracle.com \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=john.fastabend@gmail.com \
--cc=kadlec@netfilter.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nevola@gmail.com \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).