linux-kernel - Re: [PATCH 1/2] parport_pc: after superio probing restore original register values

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A3FA645.8020701@garzik.org>
Date:	Mon, 22 Jun 2009 11:41:57 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] parport_pc: after superio probing restore original
 register values

Alan Cox wrote:
> From: Jens Rottmann <JRottmann@...PERTEmbedded.de>
> 
> CONFIG_PARPORT_PC_SUPERIO probes for various superio chips by writing
> byte sequences to a set of different potential I/O ranges.  But the
> probed ranges are not exclusive to parallel ports.  Some of our boards
> just happen to have a watchdog in one of them.  Took us almost a week
> to figure out why some distros reboot without warning after running
> flawlessly for 3 hours.  For exactly 170 = 0xAA minutes, that is ...
> 
> Fixed by restoring original values after probing.  Also fixed too small
> request_region() in detect_and_report_it87().
> 
> Signed-off-by: Jens Rottmann <JRottmann@...PERTEmbedded.de>
> Signed-off-by: Alan Cox <alan@...ux.intel.com>
> Cc: <stable@...nel.org>
> ---
> 
>  drivers/parport/parport_pc.c |   31 +++++++++++++++++++++++++------
>  1 files changed, 25 insertions(+), 6 deletions(-)

Acked-by: Jeff Garzik <jgarzik@...hat.com>


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