linux-kernel - Re: [Regression 2.6.35-rc1?] Sysrq works too well (no need of alt)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100629070717.GD19712@core.coreip.homeip.net>
Date:	Tue, 29 Jun 2010 00:07:17 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Éric Piel <E.A.B.Piel@...elft.nl>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Regression 2.6.35-rc1?] Sysrq works too well (no need of alt)

On Sun, Jun 20, 2010 at 01:15:50AM +0200, Éric Piel wrote:
> Op 19-06-10 23:16, Rafael J. Wysocki schreef:
> > On Tuesday, June 08, 2010, Éric Piel wrote:
> >> Hello,
> >> I haven't investigated much yet, but I have the feeling that since
> >> 2.6.35-rc1 my "Print Screen/SysRq" key works only as SysRq: if I press
> >> it (normally assigned to take screenshot in gnome), nothing happens (no
> >> input event received in userspace) and no key on the keyboard works
> >> afterwards, until I press Alt. Actually the keys work, but behave as if
> >> the sysrq key was kept pressed (can be seen in dmesg, or by pressing "b").
> >>
> >> Looking at the log, a potential culprit is commit
> >> 97f5f0cd8cd0a05449cbb77d1e6f02e026875802 (Input: implement SysRq as a
> >> separate input handler). Probably the logic of "have to press all the
> >> keys at the same time" changed to "have to press the keys one after each
> >> other". So pressing alt and later on pressing PrintScreen leads to a SysRq.
> >>
> >> Does anybody else see this behaviour? Any suggestion on how to solve
> >> this bug? I'll try reverting the commit and report if it fixes the
> >> problem (the git revert fails so I've got to fix the conflict manually).
> > 
> > Is this still a problem with 2.6.35-rc3?
> The bug is still in 2.6.35-rc3. The patch that fixes this regression is
> in the "for-linus" branch of the input tree, but I think Dmitry hasn't
> yet sent a pull request to Linus.
> 

The fix should be in mainline now.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/