linux-kernel - Re: [PATCH] coding-style.rst: Generic alloc functions do not need OOM logging

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: <20190401150150.23d2a0f0@lwn.net>
Date:   Mon, 1 Apr 2019 15:01:50 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Joe Perches <joe@...ches.com>
Cc:     Nick Crews <ncrews@...omium.org>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-doc <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] coding-style.rst: Generic alloc functions do not need
 OOM logging

On Sat, 30 Mar 2019 10:25:03 -0700
Joe Perches <joe@...ches.com> wrote:

> Generic allocation functions already emit a dump_stack()
> so additional error logging isn't useful.
> 
> Document it as such and add a reference to the allocation
> API.
> 
> Signed-off-by: Joe Perches <joe@...ches.com>

Applied, thanks.

jon