From: Greg KH <greg@kroah.com>
To: "Zidenberg, Tsahi" <tsahee@amazon.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/2] fix userspace access on arm64 for linux 5.4
Date: Wed, 21 Apr 2021 15:26:43 +0200 [thread overview]
Message-ID: <YIAoE9fDfw18Z1oQ@kroah.com> (raw)
In-Reply-To: <66f9c439-13d1-1392-0d20-0c48fb9fdd60@amazon.com>
On Wed, Apr 21, 2021 at 04:04:12PM +0300, Zidenberg, Tsahi wrote:
>
>
> On 13/04/2021 10:27, Greg KH wrote:
> > On Mon, Apr 12, 2021 at 10:46:41PM +0300, Zidenberg, Tsahi wrote:
> >> The original bug that I was working on: command line parameters don't
> >> appear when snooping execve using bpf on arm64.
> > Has this ever worked? If not, it's not really a regression that needs
> > to be fixed, just use a newer kernel version, right?
> It's not so much a regression between old and new kernels, as it is
> a regression when changing architectures. The same API works on x86,
> but not on arm64 (in x86 - you can access userspace with a kernelspace
> access).
What API are you talking about here?
Different CPU architectures support different things. Some do not
support ebpf at all, is that a regression? No.
> Multiple Linux distributions support both x86 and arm64, and some of
> these choose to keep with 5.4 LTS Linux kernel. I think these
> distributions should expect the same experience across architectures.
Since when has that ever been a requirement of Linux?
That is not a requirement of the stable kernel trees either, please see
our very simple set of rules.
still confused as to what you are trying to do here,
greg k-h
prev parent reply other threads:[~2021-04-21 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 10:56 [PATCH 0/2] fix userspace access on arm64 for linux 5.4 Zidenberg, Tsahi
2021-03-29 10:58 ` [PATCH 1/2] bpf: fix userspace access for bpf_probe_read{, str}() Zidenberg, Tsahi
2021-03-30 17:21 ` Sasha Levin
2021-03-31 18:37 ` Zidenberg, Tsahi
2021-04-03 9:56 ` Greg KH
2021-04-04 9:13 ` Zidenberg, Tsahi
2021-04-10 11:29 ` Greg KH
2021-04-12 20:01 ` Zidenberg, Tsahi
2021-04-13 7:28 ` Greg KH
2021-03-29 10:59 ` [PATCH 2/2] tracing/kprobes: handle userspace access on unified probes Zidenberg, Tsahi
2021-04-10 11:29 ` Greg KH
2021-04-10 11:30 ` [PATCH 0/2] fix userspace access on arm64 for linux 5.4 Greg KH
2021-04-12 19:46 ` Zidenberg, Tsahi
2021-04-13 7:27 ` Greg KH
2021-04-21 13:04 ` Zidenberg, Tsahi
2021-04-21 13:26 ` Greg KH [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=YIAoE9fDfw18Z1oQ@kroah.com \
--to=greg@kroah.com \
--cc=stable@vger.kernel.org \
--cc=tsahee@amazon.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 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).