linux-kernel - Re: [PATCH] gfs2: Use kvmalloc instead of opencoded kmalloc/vmalloc

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: <CAHc6FU7VrzJ7wfTLsKZMjgkRiL7pTnwaLA4Jm4Wocm4hZwmrHQ@mail.gmail.com>
Date:   Mon, 3 Aug 2020 14:10:23 +0200
From:   Andreas Gruenbacher <agruenba@...hat.com>
To:     Denis Efremov <efremov@...ux.com>
Cc:     Bob Peterson <rpeterso@...hat.com>,
        cluster-devel <cluster-devel@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gfs2: Use kvmalloc instead of opencoded kmalloc/vmalloc

Hello,

On Sat, Aug 1, 2020 at 2:05 PM Denis Efremov <efremov@...ux.com> wrote:
> Please, skip this patch. I missed that kvmalloc checks (flags & GFP_KERNEL) == GFP_KERNEL
> before calling vmalloc.

okay. Assuming that you'll follow up with a fixed version, please also
mention that this change supplements commit 3cdcf63ed2d1 ("GFS2: use
kvfree() instead of open-coding it").

Thanks,
Andreas