linux-kernel - Re: [PATCH -rt] fix setting of preempt_max_latency and preempt

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:	Tue, 27 Mar 2007 15:39:52 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andreas Mohr <andi@...x01.fht-esslingen.de>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -rt] fix setting of preempt_max_latency and
	preempt_thresh on 64 bit systems

On Tue, 2007-03-27 at 21:15 +0200, Andreas Mohr wrote:

> Maybe fix up all the other myriads of sysctl entries which use a rather
> non-precise generic sizeof(int) as well?
> Or doesn't that make sense?

No, it does make sense

> Maybe this is because it's security relevant and you'd better make sure
> to know *exactly* the number of integers a buffer's length is supposed to be?

This is the problem. I was going to put some more time and clean up all
the stuff in there, but it will take more time than I currently have.
Since I would need to audit all the variables, and see how they would
interact in every arch.

-- Steve


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