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: <68676e00611131339l5b0dc9a2rc8e0b590aca6c162@mail.gmail.com>
Date:	Mon, 13 Nov 2006 22:39:12 +0100
From:	"Luca Tettamanti" <kronos.it@...il.com>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	"Vojtech Pavlik" <vojtech@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] atkbd: disable spurious ACK/NAK warning on panic

On 11/13/06, Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
Hi,

> On 11/13/06, Luca Tettamanti <kronos.it@...il.com> wrote:
> > After the panic() message has been printed kernel may blink keyboard
> > leds to signal the abnormal condition.
> > atkbd warns that "Some program might be trying access hardware directly"
> > at every blink, scrolling the useful text out of the screen.
> > Avoid printing the warning when oops_in_progress is set in order to
> > preserve the panic message.
>
> Current input git tree already has code in i8042 suppressing extra ACKs
> caused by panic blinks; as soon as Linus pulls from me you should not
> see these messages anymore.

Great, thanks.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ