All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, mhiramat@kernel.org,
	oleg@redhat.com, peterz@infradead.org, acme@kernel.org,
	namhyung@kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, thiago.bauermann@linaro.org,
	broonie@kernel.org, yury.khrustalev@arm.com,
	kristina.martsenko@arm.com, liaochang1@huawei.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/8] arm64: uaccess: Add additional userspace GCS accessors
Date: Wed, 23 Jul 2025 10:50:33 +0100	[thread overview]
Message-ID: <aICwaQZxK5Spjj8G@arm.com> (raw)
In-Reply-To: <20250719043740.4548-5-jeremy.linton@arm.com>

On Fri, Jul 18, 2025 at 11:37:36PM -0500, Jeremy Linton wrote:
> +/*
> + * Unlike put_user_gcs() above, the use of copy_from_user() may provide
> + * an opening for non GCS pages to be used to source data. Therefore this
> + * should only be used in contexts where that is acceptable.
> + */

Even in user space, the GCS pages can be read with normal loads, so
already usable as a data source if one wants to (not that it's of much
use). So not sure the comment here is needed.

> +static inline u64 load_user_gcs(unsigned long __user *addr, int *err)

Nitpick: name this get_user_gcs() for symmetry with put_user_gcs().

> +{
> +	unsigned long ret;
> +	u64 load = 0;
> +
> +	gcsb_dsync();

Might be worth a comment here, see the one in gcs_restore_signal().

> +	ret = copy_from_user(&load, addr, sizeof(load));
> +	if (ret != 0)
> +		*err = ret;
> +	return load;
> +}

Otherwise the patch looks fine:

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>


  reply	other threads:[~2025-07-23 10:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-19  4:37 [PATCH v4 0/8] arm64: Enable UPROBES with GCS Jeremy Linton
2025-07-19  4:37 ` [PATCH v4 1/8] arm64/gcs: task_gcs_el0_enable() should use passed task Jeremy Linton
2025-07-19  4:37 ` [PATCH v4 2/8] arm64: probes: Break ret out from bl/blr Jeremy Linton
2025-07-23  9:44   ` Catalin Marinas
2025-07-19  4:37 ` [PATCH v4 3/8] arm64: uaccess: Move existing GCS accessors definitions to gcs.h Jeremy Linton
2025-07-23  9:44   ` Catalin Marinas
2025-07-19  4:37 ` [PATCH v4 4/8] arm64: uaccess: Add additional userspace GCS accessors Jeremy Linton
2025-07-23  9:50   ` Catalin Marinas [this message]
2025-07-23 11:01     ` Mark Brown
2025-07-23 17:14     ` Jeremy Linton
2025-07-24  5:14       ` Catalin Marinas
2025-07-24 17:01         ` Mark Brown
2025-07-19  4:37 ` [PATCH v4 5/8] arm64: probes: Add GCS support to bl/blr/ret Jeremy Linton
2025-07-23 10:00   ` Catalin Marinas
2025-07-23 11:13     ` Mark Brown
2025-07-23 18:34     ` Jeremy Linton
2025-07-19  4:37 ` [PATCH v4 6/8] arm64: uprobes: Add GCS support to uretprobes Jeremy Linton
2025-07-23 10:09   ` Catalin Marinas
2025-07-24 20:41     ` Jeremy Linton
2025-07-19  4:37 ` [PATCH v4 7/8] arm64: Kconfig: Remove GCS restrictions on UPROBES Jeremy Linton
2025-07-23 10:10   ` Catalin Marinas
2025-07-19  4:37 ` [PATCH v4 8/8] uprobes: uprobe_warn should use passed task Jeremy Linton
2025-07-21 12:12   ` Oleg Nesterov
2025-07-24  8:24   ` Masami Hiramatsu
2025-07-23 16:03 ` (subset) [PATCH v4 0/8] arm64: Enable UPROBES with GCS Catalin Marinas

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=aICwaQZxK5Spjj8G@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=irogers@google.com \
    --cc=jeremy.linton@arm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kristina.martsenko@arm.com \
    --cc=liaochang1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thiago.bauermann@linaro.org \
    --cc=will@kernel.org \
    --cc=yury.khrustalev@arm.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.