linux-kernel - Re: [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode

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: <20200520183508.GI1457@zn.tnic>
Date:   Wed, 20 May 2020 20:35:08 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Reinette Chatre <reinette.chatre@...el.com>
Cc:     tglx@...utronix.de, fenghua.yu@...el.com, tony.luck@...el.com,
        kuo-lang.tseng@...el.com, ravi.v.shankar@...el.com,
        mingo@...hat.com, babu.moger@....com, hpa@...or.com,
        x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V6 0/4] x86/resctrl: Enable user to view and select
 thread throttling mode

On Wed, May 20, 2020 at 10:32:02AM -0700, Reinette Chatre wrote:
> I was told that these enhancements really needed to get into v5.8,
> otherwise the OSV intercepts will be much further out. Certainly not of
> concern to you and not your problem, I am just answering your question
> as an explanation for my goal for inclusion into v5.8.

I believe under "OSV" fall distros too and I, with my distro hat on, can
tell you that at least for us, SUSE, it suffices if the patches are in a
maintainer tree on their way upstream to start backporting them.

Which means, if they get queued in tip after 5.8 releases, that would be
like a couple of weeks later.

Dunno if the other OSVs you work with have such relaxed requirements
- just pointing out that if they do, a couple of weeks later is not a
whole cycle later.

> It seems inappropriate that I have the title of maintainer and not be
> able to have patches considered for inclusion during an entire release
> cycle.

Well, we try very hard to be fair when looking at patchsets. In your
case, I already took a patchset from you this cycle and there are other
patchsets waiting for a lot longer than yours - even patchsets from your
colleagues at Intel.

So I understand that you think it might be inappropriate but please try
to understand it also from our standpoint in that we try to round-robin
between everyone as fair as possible.

So I will try to look at yours in the next days but I cannot promise you
anything.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette