linux-kernel - Re: [PATCH V4] sched/isolation: isolate from handling managed interrupt

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, 04 Feb 2020 09:13:55 +0000
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Peter Xu <peterx@...hat.com>
Cc:     Ming Lei <ming.lei@...hat.com>, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Luiz Capitulino <lcapitulino@...hat.com>
Subject: Re: [PATCH V4] sched/isolation: isolate from handling managed interrupt

Peter,

Peter Xu <peterx@...hat.com> writes:
> On Mon, Feb 03, 2020 at 11:15:50PM +0000, Thomas Gleixner wrote:
>> No, really. The basic guarantee is that your new kernel is going to work
>> fine with the previous command line, but making a guarantee that new
>> command line options still work on an old kernel are just creating a
>> horrible mess. So if that command line interface was not designed to
>> handle unknown arguments in the first place, you better fix that.
>
> Hi, Thomas,
>
> Just to make sure I understand it right: are you suggesting that we
> fix up housekeeping_isolcpus_setup() to be able to skip unknown sub
> parameters?

Exactly.