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, 4 Dec 2016 11:20:27 +0100
From:   SF Markus Elfring <elfring@...rs.sourceforge.net>
To:     Jiri Kosina <jikos@...nel.org>
Cc:     linux-alpha@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>,
        Matt Turner <mattst88@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Richard Henderson <rth@...ddle.net>,
        Rusty Russell <rusty@...tcorp.com.au>,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: alpha: Checking for a failed kmalloc() in
 process_reloc_for_got()?

>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/alpha/kernel/module.c?id=e05f574a0bb1f4502a4b2264fdb0ef6419cf3772#n40
>>
>> Would it be useful to check the return value from a call of the
>> function “kmalloc” also there?
> 
> *drumroll* it'd actually be a proper bugfix.

Which kind of exception handling can be added here when the function
“process_reloc_for_got” has got the return type “void” so far?

Will it be needed to handle such a software failure at more source code places
by a special error code?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ