From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: john.fastabend@gmail.com, ast@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf: no need to nullify ri->map in xdp_do_redirect
Date: Thu, 17 Aug 2017 10:16:31 -0700 (PDT) [thread overview]
Message-ID: <20170817.101631.1454679823951159481.davem@davemloft.net> (raw)
In-Reply-To: <782d0b6850cb1a63230c0fd634f1e61d67a01e60.1502975082.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 17 Aug 2017 15:07:22 +0200
> We are guaranteed to have a NULL ri->map in this branch since
> we test for it earlier, so we don't need to reset it here.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Applied.
prev parent reply other threads:[~2017-08-17 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 13:07 [PATCH net-next] bpf: no need to nullify ri->map in xdp_do_redirect Daniel Borkmann
2017-08-17 15:59 ` John Fastabend
2017-08-17 17:16 ` David Miller [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=20170817.101631.1454679823951159481.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=netdev@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).