linux-kernel - Re: [GIT PULL] bounds fixes for v5.18-rc1

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] [day] [month] [year] [list]

Message-ID: <E127689C-C2F9-4B47-8B77-4A6B1533ECDF@chromium.org>
Date:   Wed, 23 Mar 2022 07:51:52 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Sakari Ailus <sakari.ailus@...ux.intel.com>
CC:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Arnd Bergmann <arnd@...db.de>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Greg Ungerer <gerg@...ux-m68k.org>,
        Guenter Roeck <linux@...ck-us.net>,
        "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        Ivan Kokshaysky <ink@...assic.park.msu.ru>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Mark Rutland <mark.rutland@....com>,
        Matt Turner <mattst88@...il.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Peter Huewe <peterhuewe@....de>,
        "Peter Zijlstra (Intel)" <peterz@...radead.org>,
        Richard Henderson <rth@...ddle.net>,
        Sean Christopherson <seanjc@...gle.com>,
        Stefan Berger <stefanb@...ux.ibm.com>
Subject: Re: [GIT PULL] bounds fixes for v5.18-rc1



On March 23, 2022 4:44:56 AM PDT, Sakari Ailus <sakari.ailus@...ux.intel.com> wrote:
>Hi Kees,
>
>On Mon, Mar 21, 2022 at 08:52:31AM -0700, Kees Cook wrote:
>>       media: omap3isp: Use struct_group() for memcpy() region
>
>This patch has been applied to linux-media tree about a month ago. It may
>have taken a bit more time than usual to get to linux-next though.
>
>Please try to remember to agree with maintainers in advance when merging
>patches via non-default routes.

Ah-ha; thank you for grabbing this one! I'm sorry I missed it while tending this tree; given the ordering of merges in -next, I've had to carry these kinds of fixes to avoid warnings popping up for various builders, but dropping accepted patches has been a manual process. I will see what I can do to automate this going forward.

-Kees

-- 
Kees Cook