From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-alpha@vger.kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>,
Matt Turner <mattst88@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Richard Henderson <rth@twiddle.net>,
Rusty Russell <rusty@rustcorp.com.au>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: alpha: Checking for a failed kmalloc() in process_reloc_for_got()?
Date: Sun, 04 Dec 2016 10:20:27 +0000 [thread overview]
Message-ID: <782323c8-7e33-39e5-ae04-a94cf454a346@users.sourceforge.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1612040108350.29400@cbobk.fhfr.pm>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 765 bytes --]
>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/alpha/kernel/module.c?idà5f574a0bb1f4502a4b2264fdb0ef6419cf3772#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
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-12-04 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 13:15 alpha: Checking for a failed kmalloc() in process_reloc_for_got()? SF Markus Elfring
2016-12-04 0:10 ` Jiri Kosina
2016-12-04 10:20 ` SF Markus Elfring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=782323c8-7e33-39e5-ae04-a94cf454a346@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox