linux-kernel - Re: [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd API

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: <alpine.DEB.2.02.1402202218351.4468@ionos.tec.linutronix.de>
Date:	Thu, 20 Feb 2014 22:21:49 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Alexey Perevalov <a.perevalov@...sung.com>
cc:	linux-kernel@...r.kernel.org, john.stultz@...aro.org,
	Anton Vorontsov <anton@...msg.org>, kyungmin.park@...sung.com,
	cw00.choi@...sung.com, akpm@...ux-foundation.org
Subject: Re: [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd
 API

On Thu, 20 Feb 2014, Alexey Perevalov wrote:

> On 02/20/2014 03:12 PM, Thomas Gleixner wrote:
> > On Thu, 20 Feb 2014, Alexey Perevalov wrote:
> > 
> > > Hello.
> > > 
> > > This is a combo patch set for support defferability in timerfd.
> > > Due implementation of timerfd is based on hrtimers and only on hrtimers,
> > > it was necessary to add such deferrability into hrtimers too.
> > Sigh, this is not about timerfd. Adding new clock ids exposes them to
> > all other hrtimer based interfaces as well.
> Posix timers, maybe something else,
> do you want to separate this patch set, or add to this patch set,
> 1. proper description
> 2. and if it'll touch posix-timer, posix_timers clocks should be extended too.

Did you even try to understand the scope of the deferrable clock id
changes?

I really wonder why you try to hack such an interface without even
remotely understanding how the related user space interfaces work.

Thanks,

	tglx


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