linux-kernel - Re: [RFC PATCH] sched: Add cpu based entries to debugfs

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: <20150331091324.GA16810@gmail.com>
Date:	Tue, 31 Mar 2015 11:13:24 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Mike Galbraith <efault@....de>,
	David Ahern <david.ahern@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs

* Peter Zijlstra <peterz@...radead.org> wrote:

> On Mon, Mar 30, 2015 at 10:43:14AM +0200, Mike Galbraith wrote:
>
> > I think it would be a good thing if we can get away with it, but I 
> > also think you could safely bet your life that somebody will 
> > squeak.
> 
> The thing I worry most about is that squeaking only happening 5 
> years later :/

So lets start by keeping the sysctl thing with the very 
scheduler-internal names, but all zeroes and no effect of any change - 
i.e. a dead API in all but appearance. I don't think there's any 
legitimate use of those, beyond debugging, as we could change the 
internal implementation anymore and moot many of those flags.

So lets trigger the squeaking that way. If any complaint comes in 
beyond 1-2 kernel releases then I don't think it's a regression, it 
turns into a feature request ...

Thanks,

        Ingo

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