All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zhan Xusheng" <zhanxusheng1024@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v5] tty: sysrq: clear the old reset sequence when reset_seq changes
Date: Fri, 30 Oct 2026 12:43:07 +0000	[thread overview]
Message-ID: <sashiko-outbox-191022@kernel.org> (raw)
In-Reply-To: <20261030123640.263164-1-zhanxusheng1024@gmail.com>

> From: Zhan Xusheng <zhanxusheng@xiaomi.com>
> 
> Changing reset_seq at runtime does not work on a keyboard that already
> used the old value, because each keyboard adds the new keys to its own
> copy instead of replacing it:
> 
>   echo 56,29,111 > /sys/module/sysrq/parameters/reset_seq # Alt+Ctrl+Del
>   (press any key)
>   echo 59,60 > /sys/module/sysrq/parameters/reset_seq     # F1+F2
> 
> F1+F2 then does nothing; only all five keys together reset.
> 
> Clear the old keys when the copy is rebuilt.  If sysrq_downtime_ms is
> set, also stop a reset the old keys already started, since releasing
> them no longer cancels it.
> 
> A key pressed while reset_seq is being written can see a partial
> sequence.  With this change that can happen on any keyboard, not only
> on ones that never used a sequence, but the window is a few
> microseconds and not worth closing.
> 
> Fixes: 154b7a489a5b ("Input: sysrq - allow specifying alternate reset sequence")
> Cc: stable@vger.kernel.org
> Assisted-by: Kiro:claude-opus-5.5
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261030123640.263164-1-zhanxusheng1024@gmail.com?part=1


      reply	other threads:[~2026-10-30 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 12:36 [PATCH v5] tty: sysrq: clear the old reset sequence when reset_seq changes Zhan Xusheng
2026-10-30 12:43 ` sashiko-bot [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=sashiko-outbox-191022@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zhanxusheng1024@gmail.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.