From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH man v4] bpf.2: various updates/follow-ups to address some fixmes
Date: Fri, 07 Aug 2015 14:31:41 +0200 [thread overview]
Message-ID: <55C4A52D.4030007@gmail.com> (raw)
In-Reply-To: <55C4809F.7020900-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
Hi Daniel,
[...]
>>>>> When a jump into the new program has been performed,
>>>>> +it won't return to the old one anymore.
>>>>> +
>>>>> +If no eBPF program is found at the given index of the program array,
>>>>
>>>> I find this language a little unclear. The array does not contain eBPF
>>>> programs, but rather file descriptors. So, what does "not found" here
>>>> really mean? (I added a FIXME.)
>>>
>>> Ok, it's a bit more complicated to explain I guess. So from user space
>>> side, a lookup on that map type is not allowed. When user space adds a
>>> new file descriptor into the prog map, the kernel internally translates
>>> that to the actual program holds reference, etc. The tail call helper is
>>> mapped into a eBPF instruction, so no real helper call here. That instruction
>>> will then have a register setting as if we'd have a function call, so it
>>> has the lookup key and uses it directly to find the array slot. From
>>> there, it has access to the actual underlying program. "Not found" means
>>> conditions mentioned as earlier above.
>>
>> Okay I've changed that paragraph to now read:
>>
>> If no eBPF program is found at the given index of the pro‐
>> gram array (because the map slot doesn't contain a valid
>> program file descriptor, the specified lookup index/key is
>> out of bounds, or the limit of 32 nested calls has been
>> exceed) execution continues with the current eBPF program.
>> This can be used as a fall-through for default cases.
>>
>> Okay?
>
> Works for me, thanks!
Thanks for checking.
> I'll drop you some more patches on remaining items, at the very latest after
> LinuxCon NA & Plumbers.
Thanks. The page is already looking a lot better than the version that went
out with the last man-pages release.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-08-07 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 22:25 [PATCH man v4] bpf.2: various updates/follow-ups to address some fixmes Daniel Borkmann
[not found] ` <e56dadb710e4beec76c02823933c232e19af025b.1438208478.git.daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-08-05 20:09 ` Michael Kerrisk (man-pages)
[not found] ` <55C26D97.6090408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-05 20:33 ` Daniel Borkmann
[not found] ` <55C2730E.1090807-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-08-07 9:40 ` Michael Kerrisk (man-pages)
[not found] ` <55C47D11.3040903-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-07 9:55 ` Daniel Borkmann
[not found] ` <55C4809F.7020900-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-08-07 12:31 ` Michael Kerrisk (man-pages) [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=55C4A52D.4030007@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.