linux-kernel - Re: [PATCH] vt: don't hardcode the mem allocation upper bound

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: <20200423134455.GA4073139@kroah.com>
Date:   Thu, 23 Apr 2020 15:44:55 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Sam Ravnborg <sam@...nborg.org>
Cc:     Nicolas Pitre <nico@...xnic.net>,
        Adam Borowski <kilobyte@...band.pl>,
        Chen Wandun <chenwandun@...wei.com>, jslaby@...e.com,
        daniel.vetter@...ll.ch, b.zolnierkie@...sung.com, lukas@...ner.de,
        ghalat@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vt: don't hardcode the mem allocation upper bound

On Fri, Apr 17, 2020 at 04:49:15PM +0200, Sam Ravnborg wrote:
> Hi Greg.
> 
> I assume you will take this patch.
> Not really drm-misc material.

Yes, will do, thanks.

greg k-h