mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	He Zhe <zhe.he@windriver.com>,
	jolsa@redhat.com, alexander.shishkin@linux.intel.com,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	namhyung@kernel.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/2] arm64: uprobe: Return EOPNOTSUPP for AARCH32 instruction probing
Date: Tue, 23 Feb 2021 15:28:39 +0000	[thread overview]
Message-ID: <161407668452.1401335.3864455032595350603.b4-ty@kernel.org> (raw)
In-Reply-To: <20210223082535.48730-1-zhe.he@windriver.com>

On Tue, 23 Feb 2021 16:25:34 +0800, He Zhe wrote:
> As stated in linux/errno.h, ENOTSUPP should never be seen by user programs.
> When we set up uprobe with 32-bit perf and arm64 kernel, we would see the
> following vague error without useful hint.
> 
> The sys_perf_event_open() syscall returned with 524 (INTERNAL ERROR:
> strerror_r(524, [buf], 128)=22)
> 
> [...]

Applied first patch only to arm64 (for-next/fixes), thanks!

[1/2] arm64: uprobe: Return EOPNOTSUPP for AARCH32 instruction probing
      https://git.kernel.org/arm64/c/d47422d953e2

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      parent reply	other threads:[~2021-02-23 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  8:25 He Zhe
2021-02-23  8:25 ` [PATCH 2/2] perf tools: Improve EOPNOTSUPP error reporting He Zhe
2021-03-03  8:30   ` He Zhe
2021-02-23 15:28 ` Will Deacon [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=161407668452.1401335.3864455032595350603.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=jolsa@redhat.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=zhe.he@windriver.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

all inboxes | Powered by JetHome®