linux-kernel - Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm

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]

Date:	Fri, 22 Jun 2007 20:18:53 -0700
From:	David Brownell <david-b@...bell.net>
To:	Tino Keitel <tino.keitel@....de>
Cc:	Alessandro Zummo <alessandro.zummo@...ertech.it>,
	rtc-linux@...glegroups.com,
	Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>,
	linux-kernel@...r.kernel.org
Subject: Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm

[ please don't edit folk off the cc list unless you *know* they
are getting duplicates ... ]

> > It's got as much documentation in the kernel tree as that
> > old /proc/acpi/alarm thing.  More, in fact, since the GIT
> > comment for the putback creating /sys/rtc/.../wakealarm
> > files has lots of info about how to use it.
> 
> What GIT comment are you referring to?

What "git log drivers/rtc/rtc-sysfs.c" shows ... date Feb 12.
The web interface shows it too.


> > One theory:  it's an RTC that doesn't support all the fields,
> > so its driver is returning "-1" in fields like "year" or "month".
>
> With the old /proc/acpi/alarm, the year 2007 became 0007. Maybe this is
> the culprit?

That's essentially the same issue.  It needs some sort
of generic fix at the rtc_read_alarm() level.


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