From: Greg KH <gregkh@linuxfoundation.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Lorenz Bauer <oss@lmb.io>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>,
bpf@vger.kernel.org
Subject: Re: Closing the BPF map permission loophole
Date: Fri, 28 Oct 2022 08:27:07 +0200 [thread overview]
Message-ID: <Y1t2OxF3o0mtF1Hm@kroah.com> (raw)
In-Reply-To: <CAEf4BzawXPiXY3mNabi0ggyTS9wtg6mh8x97=fYGhuGj4=2hnw@mail.gmail.com>
On Thu, Oct 27, 2022 at 09:54:57AM -0700, Andrii Nakryiko wrote:
> But first, two notes.
>
> 1) Backporting this is going to be hard, and I don't think that should
> be the goal, it's going to be too intrusive, probably.
Don't worry about backporting when doing your work. Get it correct
first, and let others worry about any backporting if it's even needed.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-28 6:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 10:30 Closing the BPF map permission loophole Lorenz Bauer
2022-09-16 3:03 ` Kumar Kartikeya Dwivedi
2022-09-22 14:57 ` Lorenz Bauer
2022-09-17 15:42 ` Stanislav Fomichev
2022-09-21 16:32 ` Roberto Sassu
2022-09-22 14:47 ` Lorenz Bauer
2022-09-22 15:39 ` Roberto Sassu
2022-09-22 16:21 ` Lorenz Bauer
2022-09-23 7:39 ` Roberto Sassu
2022-09-26 15:35 ` Lorenz Bauer
2022-09-26 16:18 ` Roberto Sassu
2022-09-28 8:52 ` Lorenz Bauer
2022-09-28 9:42 ` Roberto Sassu
2022-09-28 10:33 ` Toke Høiland-Jørgensen
2022-09-28 11:23 ` Roberto Sassu
2022-09-29 0:24 ` Paul Moore
2022-09-29 7:54 ` Roberto Sassu
2022-09-29 15:27 ` Casey Schaufler
2022-09-30 7:42 ` Roberto Sassu
2022-09-29 22:30 ` Paul Moore
2022-09-30 9:56 ` Roberto Sassu
2022-09-30 20:43 ` Paul Moore
2022-10-04 8:03 ` Roberto Sassu
2022-09-22 16:29 ` Lorenz Bauer
2022-09-22 23:21 ` Hao Luo
2022-09-26 15:41 ` Lorenz Bauer
2022-09-26 18:39 ` Hao Luo
2022-09-28 8:54 ` Lorenz Bauer
2022-10-06 7:15 ` Roberto Sassu
2022-10-27 16:54 ` Andrii Nakryiko
2022-10-28 6:27 ` Greg KH [this message]
2022-10-28 17:17 ` Andrii Nakryiko
2022-10-29 11:18 ` Lorenz Bauer
2022-10-31 11:53 ` Roberto Sassu
2022-11-04 21:10 ` Andrii Nakryiko
2022-11-07 12:11 ` Roberto Sassu
2022-12-12 16:10 ` Roberto Sassu
2022-12-12 17:07 ` Alexei Starovoitov
2022-12-12 18:19 ` Roberto Sassu
2022-12-16 10:23 ` Roberto Sassu
2022-12-20 20:44 ` Paul Moore
2022-12-21 9:53 ` Roberto Sassu
2022-12-22 0:55 ` Paul Moore
2023-01-10 9:11 ` Roberto Sassu
2023-01-13 23:44 ` Andrii Nakryiko
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=Y1t2OxF3o0mtF1Hm@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=oss@lmb.io \
--cc=sdf@google.com \
/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.