Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 09 Jun 2022 06:02:27 -0700
From:   Kees Cook <keescook@chromium.org>
To:     Philipp Zabel <p.zabel@pengutronix.de>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Shawn Guo <shawnguo@kernel.org>,
        Sascha Hauer <s.hauer@pengutronix.de>,
        Fabio Estevam <festevam@gmail.com>,
        David Howells <dhowells@redhat.com>
CC:     Sven Schnelle <svens@linux.ibm.com>,
        Heiko Carstens <hca@linux.ibm.com>,
        Vasily Gorbik <gor@linux.ibm.com>,
        Alexander Gordeev <agordeev@linux.ibm.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] s390: disable -Warray-bounds
User-Agent: K-9 Mail for Android
In-Reply-To: <168dbedc634a2994e9ab8f7e33930304da6140a7.camel@pengutronix.de>
References: <20220422134308.1613610-1-svens@linux.ibm.com> <202204221052.85D0C427@keescook> <CAHk-=wjahn2fZtMxmc4D9UOUGWVws1wZ=X46jrTV=_tEpzXeoA@mail.gmail.com> <202206081404.F98F5FC53E@keescook> <CAHk-=wiFn-_OaWKY=nXt3YSiy=obrNoQW_u7zKO7qoArez=GUw@mail.gmail.com> <AEEBCF5D-8402-441D-940B-105AA718C71F@chromium.org> <168dbedc634a2994e9ab8f7e33930304da6140a7.camel@pengutronix.de>
Message-ID: <B392D155-E64C-4EBC-9C6C-4290F637F382@chromium.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On June 9, 2022 2:56:47 AM PDT, Philipp Zabel <p=2Ezabel@pengutronix=2Ede>=
 wrote:
>Hi Kees,
>
>On Mi, 2022-06-08 at 17:39 -0700, Kees Cook wrote:
>[=2E=2E=2E]
>> > See the attached patch for
>> >=20
>> > (a) make the s390 "use -Wno-array-bounds for gcc-12" be generic
>> >=20
>> > (b) fix the ipuv3-crtc=2Ec one=2E IMX people?
>> >=20
>> > (c) disable -Wdangling-pointer entirely for now
>>=20
>> I'll take a look; thanks! Should I send them back as a pull request?
>
>Does this refer to the whole patch, including (a) and (b), or am I to
>pick up the ipuv3-crtc=2Ec fix?

Go ahead and grab that one please; that's more "normal" :)

Thanks!


--=20
Kees Cook