From: Nick Bowler <nbowler@draconx.ca>
To: linux-kernel@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Alexey Gladkov <legion@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: PROBLEM: kbd busted in linux 6.10-rc1 (regression)
Date: Wed, 29 May 2024 00:45:56 -0400 [thread overview]
Message-ID: <ad4e561c-1d49-4f25-882c-7a36c6b1b5c0@draconx.ca> (raw)
Hi,
It seems kbd utilities are all broken on linux 6.10-rc1. For example:
# loadkeys en-latin9
Couldn't get a file descriptor referring to the console.
[and it did not change the console keymap]
This is a regression from linux 6.9. If I run strace on a working
kernel, at the point of the first difference we see:
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {c_iflag=BRKINT|ICRNL|IXON|IMAXBEL|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD|HUPCL, c_lflag=, ...}) = 0
ioctl(3, KDGKBTYPE, [KB_101]) = 0
...
On a busted kernel, we get:
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {c_iflag=IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD|HUPCL, c_lflag=, ...}) = 0
ioctl(3, KDGKBTYPE, 0xffceaebb) = -1 ENOTTY (Inappropriate ioctl for device)
close(3) = 0
...
A very similar problem occurs with kbd_mode, chvt, etc.
Bisection implicates the following:
8c467f3300591a206fa8dcc6988d768910799872 is the first bad commit
commit 8c467f3300591a206fa8dcc6988d768910799872
Author: Alexey Gladkov <legion@kernel.org>
Date: Wed Apr 17 19:37:35 2024 +0200
VT: Use macros to define ioctls
All other headers use _IOC() macros to describe ioctls for a long time
now. This header is stuck in the last century.
Simply use the _IO() macro. No other changes.
Signed-off-by: Alexey Gladkov <legion@kernel.org>
Link: https://lore.kernel.org/r/e4229fe2933a003341e338b558ab1ea8b63a51f6.1713375378.git.legion@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reverting this commit corrects the issue.
This testing was done on my sparc system in case it matters.
Let me know if you need any more info!
Thanks,
Nick
next reply other threads:[~2024-05-29 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 4:45 Nick Bowler [this message]
2024-05-29 5:25 ` Al Viro
2024-05-29 5:36 ` Nick Bowler
2024-05-29 6:36 ` Al Viro
2024-05-29 6:39 ` Al Viro
2024-05-29 6:04 ` Greg Kroah-Hartman
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=ad4e561c-1d49-4f25-882c-7a36c6b1b5c0@draconx.ca \
--to=nbowler@draconx.ca \
--cc=gregkh@linuxfoundation.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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®