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: <CAHk-=wiUA_3pO2jSsMZauVibx20fSdZV+aan217fy+MuGDJT8A@mail.gmail.com>
Date:   Mon, 10 Oct 2022 10:39:06 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     David Rientjes <rientjes@...gle.com>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Christoph Lameter <cl@...ux.com>,
        Pekka Enberg <penberg@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>, patches@...ts.linux.dev,
        Roman Gushchin <roman.gushchin@...ux.dev>,
        Hyeonggon Yoo <42.hyeyoo@...il.com>,
        Kees Cook <keescook@...omium.org>,
        Feng Tang <feng.tang@...el.com>
Subject: Re: [GIT PULL] slab changes for 6.1-rc1

On Mon, Oct 3, 2022 at 9:07 AM Vlastimil Babka <vbabka@...e.cz> wrote:
>
> This time I tried using topic branches much more than previously, hopefully in
> an acceptable way. After rc5-ish I also tried to stabilize their merging into
> for-next (and thus the resulting for-6.1) as well. Hence branches
> slab/for-6.1/trivial and slab/for-6.1/slub_validation_locking appear to be
> merged twice due an extra cleanup and fix, respectivelly, being added and
> merged only last week. In slab/for-6.1/kmalloc_size_roundup I however decided
> for squashing a fix last week [1] to avoid needless build errors while bisecting.

Looks good to me. And thanks to the topic branches, you can actually
see the different series (particularly that "common kmalloc" one
clearly in the history.

Thanks,

                  Linus

Powered by blists - more mailing lists