netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	stephen@networkplumber.org
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next v2 4/5] {f,m}_bpf: allow updates on program arrays
Date: Thu, 26 Nov 2015 16:51:55 +0100	[thread overview]
Message-ID: <56572A9B.7080302@iogearbox.net> (raw)
In-Reply-To: <1448551169.889784.450810993.378A2FDF@webmail.messagingengine.com>

On 11/26/2015 04:19 PM, Hannes Frederic Sowa wrote:
> On Thu, Nov 26, 2015, at 15:38, Daniel Borkmann wrote:
[...]
> Why does user space actually still have to deal with setting the mount
> point private? Isn't this handled by the kernel?
>
>> +       if (mount("bpf", target, "bpf", 0, NULL)) {
>> +               fprintf(stderr, "mount -t bpf bpf %s failed: %s\n",
>> +                       target, strerror(errno));
>> +               return -1;
>> +       }
>
> Shouldn't this be just enough?

Note that the patch just moves the function around, but to get to your
question, that would just make it shared by default, not private.

Thanks,
Daniel

  reply	other threads:[~2015-11-26 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 14:38 [PATCH iproute2 -next v2 0/5] BPF updates Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 1/5] {f,m}_bpf: make tail calls working Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 2/5] {f,m}_bpf: check map attributes when fetching as pinned Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 3/5] {f,m}_bpf: allow for user-defined object pinnings Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 4/5] {f,m}_bpf: allow updates on program arrays Daniel Borkmann
2015-11-26 15:19   ` Hannes Frederic Sowa
2015-11-26 15:51     ` Daniel Borkmann [this message]
2015-11-26 14:38 ` [PATCH iproute2 -next v2 5/5] {f,m}_bpf: add more example code Daniel Borkmann
2015-11-29 19:56   ` Stephen Hemminger

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=56572A9B.7080302@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).