linux-kernel - Re: [PATCH] ARM: mvebu: check the validation of 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]

Date:   Sun, 1 May 2022 15:01:58 +0800
From:   <xkernel.wang@...mail.com>
To:     <linux@...linux.org.uk>
Cc:     <andrew@...n.ch>, <gregory.clement@...tlin.com>,
        <sebastian.hesselbarth@...il.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: mvebu: check the validation of memory allocation

On Friday, April 29, 2022 11:19 PM +0800, linux@...linux.org.uk wrote:
> Are these failures silent, or will they be reported in the kernel log to
> make their failure obvious to those who debug the kernel?

According to chapter 14 of the coding style document:
"These generic allocation functions all emit a stack dump on failure when used
without __GFP_NOWARN so there is no use in emitting an additional failure
message when NULL is returned."

I think that these failures are not silent since __GFP_NOWARN is not
enabled.

Regards,
Xiaoke Wang