linux-kernel - Re: [PATCH] kernel/trace: Delete five error messages for a failed memory allocation

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: <1507580409.3552.15.camel@perches.com>
Date:   Mon, 09 Oct 2017 13:20:09 -0700
From:   Joe Perches <joe@...ches.com>
To:     Steven Rostedt <rostedt@...dmis.org>,
        SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc:     kernel-janitors@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kernel/trace: Delete five error messages for a failed
 memory allocation

On Mon, 2017-10-09 at 16:13 -0400, Steven Rostedt wrote:
> On Sat, 7 Oct 2017 16:15:14 +0200
> SF Markus Elfring <elfring@...rs.sourceforge.net> wrote:
> 
> > From: Markus Elfring <elfring@...rs.sourceforge.net>
> > Date: Sat, 7 Oct 2017 16:10:06 +0200
> > 
> > Omit extra messages for a memory allocation failure in these functions.
> 
> Does memory allocation failures have printk messages? If not, then I
> think this is removing useful information.

Every k.alloc failure without __GFP_NOWARN does a dump_stack()