linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Cc: linux-tip-commits@vger.kernel.org,
	Dmitry Vyukov <dvyukov@google.com>,
	x86@kernel.org
Subject: [PATCH] syscall_user_dispatch: Fix grammar in task_set_syscall_user_dispatch()
Date: Sat, 14 Jun 2025 08:59:30 +0200	[thread overview]
Message-ID: <aE0d0uuAxaeCE-9l@gmail.com> (raw)
In-Reply-To: <174983307181.406.10132559995641241207.tip-bot2@tip-bot2>


* tip-bot2 for Dmitry Vyukov <tip-bot2@linutronix.de> wrote:

> +	/*
> +	 * access_ok() will clear memory tags for tagged addresses
> +	 * if current has memory tagging enabled.
> +	 *
> +	 * To enable a tracer to set a tracees selector the
> +	 * selector address must be untagged for access_ok(),
> +	 * otherwise an untagged tracer will always fail to set a
> +	 * tagged tracees selector.
> +	 */

Typo/grammar fixes below. (And feel free to squash this fixlet into the 
originator commit.)

Thanks,

	Ingo

==================================>

Signed-off-by: Ingo Molnar <mingo@kernel.org>

 kernel/entry/syscall_user_dispatch.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/entry/syscall_user_dispatch.c b/kernel/entry/syscall_user_dispatch.c
index a9055eccb27e..d5363bc768fe 100644
--- a/kernel/entry/syscall_user_dispatch.c
+++ b/kernel/entry/syscall_user_dispatch.c
@@ -106,10 +106,10 @@ static int task_set_syscall_user_dispatch(struct task_struct *task, unsigned lon
 	 * access_ok() will clear memory tags for tagged addresses
 	 * if current has memory tagging enabled.
 	 *
-	 * To enable a tracer to set a tracees selector the
+	 * To enable a tracer to set a tracee's selector, the
 	 * selector address must be untagged for access_ok(),
 	 * otherwise an untagged tracer will always fail to set a
-	 * tagged tracees selector.
+	 * tagged tracee's selector.
 	 */
 	if (mode != PR_SYS_DISPATCH_OFF && selector &&
 		!access_ok(untagged_addr(selector), sizeof(*selector)))

  reply	other threads:[~2025-06-14  6:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1747839857.git.dvyukov@google.com>
2025-05-21 15:04 ` [PATCH v3 1/3] selftests: Fix errno checking in syscall_user_dispatch test Dmitry Vyukov
2025-06-13 16:44   ` [tip: core/entry] " tip-bot2 for Dmitry Vyukov
2025-05-21 15:04 ` [PATCH v3 2/3] syscall_user_dispatch: Add PR_SYS_DISPATCH_INCLUSIVE_ON Dmitry Vyukov
2025-06-13 16:44   ` [tip: core/entry] " tip-bot2 for Dmitry Vyukov
2025-06-14  6:59     ` Ingo Molnar [this message]
2025-05-21 15:04 ` [PATCH v3 3/3] selftests: Add tests for PR_SYS_DISPATCH_INCLUSIVE_ON Dmitry Vyukov
2025-06-13 16:44   ` [tip: core/entry] " tip-bot2 for Dmitry Vyukov

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=aE0d0uuAxaeCE-9l@gmail.com \
    --to=mingo@kernel.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).