linux-kernel - Re: RTC_DRV_CMOS can break userspace interface

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]

Date:	Fri, 1 Jun 2007 13:54:23 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Linux Kernel list <linux-kernel@...r.kernel.org>
Cc:	david-b@...bell.net
Subject: Re: RTC_DRV_CMOS can break userspace interface

On Fri, Jun 01, 2007 at 09:46:06AM +0200, Tino Keitel wrote:
> Yes, you are right. I think this issue should be covered by Kconfig.
> 
> However:
> 
> $ cat wakealarm 
> cat: wakealarm: Input/output error
> 
> It worked with /proc/acpi/alarm before.

Can you do 

for i in /sys/bus/pnp/devices/*; do if [ "$(cat $i/id)" = PNP0b00 ]; 
then cat $i/resources; echo options; cat $i/options; fi; done

and provide the output? It sounds like you have the same problem I do, 
that is that you have no IRQ listed in the PNP table.

Though, actually, on reading the code:

The code for checking for a platform device only gets included if 
CONFIG_PNP isn't set! David, surely this should be a runtime thing 
rather than a compile-time one? Right now building a kernel with PNP 
support will break horribly if it's then run on a non-PNP system...

-- 
Matthew Garrett | mjg59@...f.ucam.org
-
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/