linux-kernel - Re: [PATCH 1/6] cputime: Fix nsecs_to

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:	Wed, 12 Mar 2014 03:14:56 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Rik van Riel <riel@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 1/6] cputime: Fix nsecs_to_cputime() return type cast

On Thu, Mar 06, 2014 at 01:57:17PM -0500, Rik van Riel wrote:
> On 03/06/2014 12:56 PM, Frederic Weisbecker wrote:
> >Even though nsec based cputime_t maps to u64, nsecs_to_cputime() must
> >return a cputime_t value. We want to enforce this kind of cast in order
> >to track down buggy manipulations of cputime_t such as direct access
> >of its values under wrong assumptions on its backend type (nsecs,
> >jiffies, etc...) by core code.
> >
> >Cc: Ingo Molnar <mingo@...nel.org>
> >Cc: Marcelo Tosatti <mtosatti@...hat.com>
> >Cc: Peter Zijlstra <peterz@...radead.org>
> >Cc: Thomas Gleixner <tglx@...utronix.de>
> >Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> 
> Acked-by: Rik van Riel <riel@...hat.com>
> 

Thanks a lot for your acks. I added them for the pull request.
Unfortunately git-send-email ignored them for the Cc (it seems to
depend on the version).

But the pull request can be found there: http://marc.info/?i=1394590202-772-1-git-send-email-fweisbec%40gmail.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/