From: Marijn Suijten <marijn.suijten@somainline.org>
To: phone-devel@vger.kernel.org, Rob Herring <robh@kernel.org>
Cc: Marijn Suijten <marijns95@gmail.com>,
linux-kernel@vger.kernel.org,
Amit Pundir <amit.pundir@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH 2/2] config: android-recommended: Disable BPF_UNPRIV_DEFAULT_OFF for netd
Date: Wed, 2 Feb 2022 10:38:58 +0100 [thread overview]
Message-ID: <20220202093858.cmkm2z5w2fum6jit@SoMainline.org> (raw)
In-Reply-To: <20220202093355.108460-2-marijn.suijten@somainline.org>
On 2022-02-02 10:33:55, Marijn Suijten wrote:
> From: Marijn Suijten <marijns95@gmail.com>
Feel free to disregard this `From:` override, didn't catch it when
preparing the patches from a different machine.
- Marijn
> AOSP's `netd` process fails to start on Android S:
>
> E ClatdController: getClatEgress4MapFd() failure: Operation not permitted
> I netd : Initializing ClatdController: 410us
> E netd : Failed to start trafficcontroller: (Status[code: 1, msg: "Pinned map not accessible or does not exist: (/sys/fs/bpf/map_netd_cookie_tag_map): Operation not permitted"])
> E netd : CRITICAL: sleeping 60 seconds, netd exiting with failure, crash loop likely!
>
> And on Android R:
>
> I ClatdController: 4.9+ kernel and device shipped with P - clat ebpf might work.
> E ClatdController: getClatEgressMapFd() failure: Operation not permitted
> I netd : Initializing ClatdController: 1409us
> E netd : Failed to start trafficcontroller: (Status[code: 1, msg: "Pinned map not accessible or does not exist: (/sys/fs/bpf/map_netd_cookie_tag_map): Operation not permitted"])
>
> These permission issues are caused by 08389d888287 ("bpf: Add kconfig
> knob for disabling unpriv bpf by default") because AOSP does not provide
> netd the `SYS_ADMIN` capability, and also has no userspace support for
> the `BPF` capability yet.
>
> Cc: Amit Pundir <amit.pundir@linaro.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Suggested-by: John Stultz <john.stultz@linaro.org>
> [John suggested this in https://linaro.atlassian.net/browse/ACK-107?focusedCommentId=117382]
> Signed-off-by: Marijn Suijten <marijn.suijten@somainline.org>
> ---
> kernel/configs/android-recommended.config | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/configs/android-recommended.config b/kernel/configs/android-recommended.config
> index 22bd76e43aca..e400fbbc8aba 100644
> --- a/kernel/configs/android-recommended.config
> +++ b/kernel/configs/android-recommended.config
> @@ -1,4 +1,5 @@
> # KEEP ALPHABETICALLY SORTED
> +# CONFIG_BPF_UNPRIV_DEFAULT_OFF is not set
> # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
> # CONFIG_INPUT_MOUSE is not set
> # CONFIG_LEGACY_PTYS is not set
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-02-02 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 9:33 Marijn Suijten
2022-02-02 9:38 ` Marijn Suijten [this message]
2022-02-02 9:43 ` Greg Kroah-Hartman
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=20220202093858.cmkm2z5w2fum6jit@SoMainline.org \
--to=marijn.suijten@somainline.org \
--cc=amit.pundir@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijns95@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®