Linux Input/HID development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: jirislaby@kernel.org, dmitry.torokhov@gmail.com,
	mathieu.poirier@linaro.org, linux-serial@vger.kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhanxusheng@xiaomi.com
Subject: Re: [PATCH v4 1/2] tty: sysrq: don't expose a partially written reset_seq
Date: Fri, 30 Oct 2026 12:48:16 +0100	[thread overview]
Message-ID: <2026103055-ferocity-uselessly-cb34@gregkh> (raw)
In-Reply-To: <20261030113356.248358-1-zhanxusheng1024@gmail.com>

On Fri, Oct 30, 2026 at 07:33:56PM +0800, Zhan Xusheng wrote:
> Hi Greg,
> 
> On Fri, Oct 30, 2026 at 09:33:41AM +0100, Greg KH wrote:
> > So this feature has never worked?  Or it is just "one change only"?  So
> > your change is an addition to the feature, not a bugfix?
> 
> It is a fix.  154b7a489a5b ("Input: sysrq - allow specifying alternate
> reset sequence") added reset_seq as a writable parameter, together with
> a version counter so that each keyboard rereads the sequence after a
> write.  The reread just never clears the old keys, so on a keyboard
> that already used the old value, a new one has never worked.  Hardly
> anyone changes it at runtime, which is likely why nobody noticed.
> 
> > So this isn't a "real" issue?  If you are modifying the key sequence,
> > how can you press the key at the same time?  Doing "major" rework for
> > that might just not be worth it.
> 
> Agreed, please drop 1/2.  With only 2/2, that race can hit any
> keyboard, not only ones that never used a sequence.  Do you want 2/2
> resent on its own?

Please resend whatever you feel should actually be applied, with better
changelog text explaining all of this.

thanks,

greg k-h

  reply	other threads:[~2026-10-30 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  4:58 [PATCH v4 0/2] tty: sysrq: fix the reset sequence kept per input device Zhan Xusheng
2026-10-30  4:58 ` [PATCH v4 1/2] tty: sysrq: don't expose a partially written reset_seq Zhan Xusheng
2026-10-30  6:05   ` Greg KH
2026-10-30  6:30     ` Zhan Xusheng
2026-10-30  7:02       ` Greg KH
2026-10-30  7:58         ` Zhan Xusheng
2026-10-30  8:33           ` Greg KH
2026-10-30 11:33             ` Zhan Xusheng
2026-10-30 11:48               ` Greg KH [this message]
2026-10-30  4:58 ` [PATCH v4 2/2] tty: sysrq: reset the per-device key state when reparsing reset_seq Zhan Xusheng

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=2026103055-ferocity-uselessly-cb34@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=zhanxusheng1024@gmail.com \
    --cc=zhanxusheng@xiaomi.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