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
| ||
|
Date: Sun, 10 Dec 2017 18:05:31 -0800 From: Joe Perches <joe@...ches.com> To: "Maciej W. Rozycki" <macro@...ux-mips.org>, SF Markus Elfring <elfring@...rs.sourceforge.net> Cc: linux-mips@...ux-mips.org, Ralf Bächle <ralf@...ux-mips.org>, LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org Subject: Re: [PATCH] TC: Delete an error message for a failed memory allocation in tc_bus_add_devices() On Sun, 2017-12-10 at 21:41 +0000, Maciej W. Rozycki wrote: > On Sun, 10 Dec 2017, SF Markus Elfring wrote: > > > Omit an extra message for a memory allocation failure in this function. > > > > This issue was detected by using the Coccinelle software. > > And the problem here is? Markus' terrible commit messages. Generically, any OOM via a malloc like call has a dump_stack() which shows a stack trace unless __GFP_NOWARN is used. So this message is generally unnecessary as the dump_stack() will show the tc_bus_add_devices function name and (now hashed) value of the function address. What will be different is the particular slot # of the tc_dev will no longer be shown. Really though, if there's an OOM on the init, there are larger problems and the system will be unusable.
Powered by blists - more mailing lists