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
| ||
|
Date: Thu, 21 Feb 2013 21:57:46 -0800 From: Kevin Hilman <khilman@...aro.org> To: Frederic Weisbecker <fweisbec@...il.com> Cc: Mats Liljegren <mats.liljegren@...a.com>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linaro-dev@...ts.linaro.org, Peter Zijlstra <peterz@...radead.org>, Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [RFC/PATCH 2/5] kernel_cpustat: convert to atomic 64-bit accessors Frederic Weisbecker <fweisbec@...il.com> writes: > 2013/2/21 Frederic Weisbecker <fweisbec@...il.com>: >> 2013/2/21 Kevin Hilman <khilman@...aro.org>: >>> Subject: [PATCH 2/5] kernel_cpustat: convert to atomic 64-bit accessors >>> >>> Use the atomic64_* accessors for all the kernel_cpustat fields to >>> ensure atomic access on non-64 bit platforms. >>> >>> Thanks to Mats Liljegren for CGROUP_CPUACCT related fixes. >>> >>> Cc: Mats Liljegren <mats.liljegren@...a.com> >>> Signed-off-by: Kevin Hilman <khilman@...aro.org> >> >> Funny stuff, I thought struct kernel_cpustat was made of cputime_t >> field. Actually it's u64. So the issue is independant from the new >> full dynticks cputime accounting. It was already broken before. >> >> But yeah that's not the point, we still want to fix this anyway. But >> let's just treat this patch as independant. OK, I just sent an updated series based on your proposal. Thanks for the review, Kevin -- 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/
Powered by blists - more mailing lists