linux-kernel - Re: [PATCHv6 00/16] pps: several fixes and improvements

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, 17 Dec 2010 17:14:52 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alexander Gordeev <lasaine@....cs.msu.su>
Cc:	linux-kernel@...r.kernel.org,
	"Nikita V\. Youshchenko" <yoush@...msu.su>,
	linuxpps@...enneenne.com, Rodolfo Giometti <giometti@...eenne.com>
Subject: Re: [PATCHv6 00/16] pps: several fixes and improvements

On Sat, 18 Dec 2010 04:00:01 +0300
Alexander Gordeev <lasaine@....cs.msu.su> wrote:

> __ Fri, 17 Dec 2010 16:19:38 -0800
> Andrew Morton <akpm@...ux-foundation.org> __________:
> 
> > On Fri, 17 Dec 2010 22:54:24 +0300
> > Alexander Gordeev <lasaine@....cs.msu.su> wrote:
> > 
> > > There is one problem however: kernel consumer works bad (if enabled)
> > > when CONFIG_NO_HZ is enabled. The reason for this is commit
> > > a092ff0f90cae22b2ac8028ecd2c6f6c1a9e4601. Without it hardpps() is able
> > > to sync to 1us precision in about 10 seconds. With CONFIG_NO_HZ it is
> > > not syncing at all. This only affects patches 12-14, others are ok.
> > 
> > Is someone working on fixing all this?
> 
> Not right now but it is planned. I can only ensure that users can never
> select CONFIG_NO_HZ and CONFIG_NTP_PPS at the same time. Is it ok?

That's much better than permitting a subtly broken driver.

CONFIG_NO_HZ is pretty common nowadays, methinks.
--
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/