linux-kernel - Re: [regression, bisected] SysRq commands trigger without holding sysrq.

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: <AANLkTilDmY1DDDFlASWM2BnECgVvhszWVRuvXEY4Ty_6@mail.gmail.com>
Date:	Sun, 27 Jun 2010 08:05:18 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [regression, bisected] SysRq commands trigger without holding 
	sysrq.

On Sun, Jun 27, 2010 at 7:12 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Mon, 14 Jun 2010, Nick Bowler wrote:
>>
>> 97f5f0cd8cd0a05449cbb77d1e6f02e026875802 is the first bad commit
>
> Dmitry? I didn't see any follow-ups on this issue, should I just do the
> revert, or is there some better fix?
>
> There's another report about this from Éric Piel.

Ahh. Never mind. It should be fixed by commit f5dec51172b8 ("Input:
sysrq - fix "stuck" SysRq mode") that was in your pull request that I
already had in my queue. I just hadn't gone through all my mail yet.

                               Linus
--
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/