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  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]
Date:   Wed, 19 Aug 2020 21:44:56 -0400
From:   Joel Fernandes <>
To:     Kees Cook <>
Cc:, Aaron Lu <>,
        Aubrey Li <>,
        Julien Desfossez <>,
        "Paul E. McKenney" <>,
        Paul Turner <>,
        Peter Zijlstra <>,
        Steven Rostedt <>,
        Thomas Gleixner <>,
        Tim Chen <>,
        Tim Chen <>,
        Vincent Guittot <>,
        Vineeth Pillai <>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <>,,,
        Phil Auld <>,
        Valentin Schneider <>,
        Paolo Bonzini <>,
        Chen Yu <>,
        Christian Brauner <>
Subject: Re: [PATCH RFC 00/12] Core-sched v6+: kernel protection and hotplug

On Wed, Aug 19, 2020 at 11:26:48AM -0700, Kees Cook wrote:
> On Fri, Aug 14, 2020 at 11:18:56PM -0400, Joel Fernandes (Google) wrote:
> > This series is continuation of main core-sched v6 series [1] and adds support
> - Is this really "RFC"? Seeing multiple authors implies this is looking
>   to get merged. :)

This mini series was inspired by discussions/concerns mostly by Thomas so
that's why I kept it as RFC since I thought more comments will come.

> - Is this on top of the v6 core-sched series (or instead of)? (That
>   series doesn't seem to be RFC any more either, IMO, if it's at v6.) If
>   this replaces that series, isn't this v7? I don't see the v6
>   core-sched series in -next anywhere?

Yes, it was just a continuation of that. Actually I screwed up, I should have
just posted the whole v6 again with these patches with appropriate
subject-prefix. That would prevent confusion.

> - Whatever the case, please include the series version in the "[PATCH vN ...]"
>   portion of the Subject, otherwise things like "b4" don't really know what's
>   happening.

Got it.

> Sorry for the drive-by comments, but I was really confused trying to
> understand how this fit together. :)

No problem, your comments are very valid so they are welcome :)


 - Joel

> -- 
> Kees Cook

Powered by blists - more mailing lists