[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210608135327.be8a120ba3b1686bc62e6d7e@linux-foundation.org>
Date: Tue, 8 Jun 2021 13:53:27 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: Vlastimil Babka <vbabka@...e.cz>, Marco Elver <elver@...gle.com>,
Christoph Lameter <cl@...ux.com>,
"Lin, Zhenpeng" <zplin@....edu>, Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Roman Gushchin <guro@...com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v4 0/3] Actually fix freelist pointer vs redzoning
On Tue, 8 Jun 2021 11:39:52 -0700 Kees Cook <keescook@...omium.org> wrote:
> This fixes redzoning vs the freelist pointer (both for middle-position
> and very small caches). Both are "theoretical" fixes, in that I see no
> evidence of such small-sized caches actually be used in the kernel, but
> that's no reason to let the bugs continue to exist, especially since
> people doing local development keep tripping over it. :)
So I don't think this is suitable -stable material?
It's a bit odd that patches 2&3 were cc:stable but #1 was not. Makes
one afraid that 2&3 might have had a dependency anyway.
So I'm thinking that the whole series can just be for 5.14-rc1, in the
sent order.
Powered by blists - more mailing lists