From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com, dborkman@redhat.com
Subject: Re: [PATCH net-next] filter: do not output bpf image address for security reason
Date: Sun, 19 May 2013 23:57:00 -0700 (PDT) [thread overview]
Message-ID: <20130519.235700.216729402838504491.davem@davemloft.net> (raw)
In-Reply-To: <1368845857.3301.148.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 17 May 2013 19:57:37 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> Do not leak starting address of BPF JIT code for non root users,
> as it might help intruders to perform an attack.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied.
next prev parent reply other threads:[~2013-05-20 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 2:57 [PATCH net-next] filter: do not output bpf image address for security reason Eric Dumazet
2013-05-20 6:57 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-17 23:31 Eric Dumazet
2013-05-17 23:42 ` Joe Perches
2013-05-17 23:48 ` Eric Dumazet
2013-05-18 1:11 ` Ben Hutchings
2013-05-18 1:27 ` David Miller
2013-05-18 2:55 ` Eric Dumazet
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=20130519.235700.216729402838504491.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@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