[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec387c6d-acc7-6696-ba17-bb8792090136@embeddedor.com>
Date: Thu, 5 Jan 2023 17:14:23 -0600
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Kees Cook <keescook@...omium.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Alex Sierra <alex.sierra@....com>,
Felix Kuehling <Felix.Kuehling@....com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Shiyang Ruan <ruansy.fnst@...itsu.com>, linux-mm@...ck.org,
Alistair Popple <apopple@...dia.com>,
Joao Martins <joao.m.martins@...cle.com>,
Mike Rapoport <rppt@...nel.org>, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] memremap: Replace 0-length array with flexible array
On 1/5/23 16:41, Kees Cook wrote:
> On Thu, Jan 05, 2023 at 04:14:05PM -0600, Gustavo A. R. Silva wrote:
>> I think this is the same patch:
>>
>> https://lore.kernel.org/linux-hardening/YxKO%2FjY1x0xTpl4r@work/
>>
>> It's actually in linux-next.
>
> Hm, it's been in -next since September? Is this in a tree of yours that
> didn't get pulled for v6.2?
No. I didn't send it. It's just one of the two patches I have in my -next
tree. They didn't look like high priority at the time.
--
Gustavo
Powered by blists - more mailing lists