From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Alex Sierra <alex.sierra@amd.com>,
Felix Kuehling <Felix.Kuehling@amd.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Shiyang Ruan <ruansy.fnst@fujitsu.com>,
linux-mm@kvack.org, Alistair Popple <apopple@nvidia.com>,
Joao Martins <joao.m.martins@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] memremap: Replace 0-length array with flexible array
Date: Thu, 5 Jan 2023 18:02:32 -0600 [thread overview]
Message-ID: <Y7dlGEm3lWBjpFkG@work> (raw)
In-Reply-To: <202301051536.1D1F92678@keescook>
On Thu, Jan 05, 2023 at 03:37:03PM -0800, Kees Cook wrote:
> On Thu, Jan 05, 2023 at 05:14:23PM -0600, Gustavo A. R. Silva wrote:
> >
> >
> > 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.
>
> Cool. I'd like to get -fstrict-flex-arrays=3 finished this devel cycle,
> if possible. Can you add this one too?
>
> https://lore.kernel.org/lkml/YzIc8z+QaHvqPjLX@work
Done!
https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git/log/?h=for-next/kspp
>
> I don't see it in patchwork which I find confusing too. :P
mmh... and I don't remember updating it in patchwork before.
(thinkingface)
--
Gustavo
next prev parent reply other threads:[~2023-01-06 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 22:01 [PATCH] memremap: Replace 0-length array with flexible array Kees Cook
2023-01-05 22:14 ` Gustavo A. R. Silva
2023-01-05 22:39 ` Kees Cook
2023-01-05 22:41 ` Kees Cook
2023-01-05 23:14 ` Gustavo A. R. Silva
2023-01-05 23:37 ` Kees Cook
2023-01-06 0:02 ` Gustavo A. R. Silva [this message]
2023-01-05 22:14 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7dlGEm3lWBjpFkG@work \
--to=gustavoars@kernel.org \
--cc=Felix.Kuehling@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alex.sierra@amd.com \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=gustavo@embeddedor.com \
--cc=joao.m.martins@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=ruansy.fnst@fujitsu.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.