linux-kernel - Re: [PATCH] bus: ti-sysc: Use 2-factor allocator arguments

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

Message-ID: <20180702112719.GU112168@atomide.com>
Date:   Mon, 2 Jul 2018 04:27:19 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] bus: ti-sysc: Use 2-factor allocator arguments

* Kees Cook <keescook@...omium.org> [180627 21:59]:
> On Mon, Jun 18, 2018 at 10:45 AM, Kees Cook <keescook@...omium.org> wrote:
> > This adjusts the allocator calls to use 2-factor argument call style, as
> > done treewide already for improved defense against allocation overflows.
> >
> > Signed-off-by: Kees Cook <keescook@...omium.org>
> 
> Friendly ping! :) This is the last 2-factor devm* allocation left in
> 4.18 to be fixed.

Sorry for the delay on this one. As we're already at -rc3, I'll apply
this into omap-for-v4.19/ti-sysc. Seems there should not be need to rush
this into v4.18-rc cycle, but please do let me know if that is not the
case.

Regards,

Tony