From: SF Markus Elfring <elfring@users.sourceforge.net>
To: shuah@kernel.org, linux-kselftest@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: selftests: Completion of error handling
Date: Tue, 21 Nov 2017 20:30:14 +0100 [thread overview]
Message-ID: <dc266850-52d0-8380-7ab1-087c07a709fb@users.sourceforge.net> (raw)
In-Reply-To: <26965dfd-74e8-cf6f-7f55-56310834189d@kernel.org>
>> Static source code analysis points out that the checking of return values from
>> some function calls is incomplete also in this software area.
>> How would you like to fix remaining open issues there?
>>
>
> Without understanding the details on which failures,
Are you using any dedicated tools for this purpose already?
> it would be hard for me comment on how to handle them.
I inspected also another specific source file for example.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/tools/testing/selftests/timers/posix_timers.c?id=aa1fbe633d3034f9f838ff13387af04771e68e31#n81
https://elixir.free-electrons.com/linux/v4.14-rc8/source/tools/testing/selftests/timers/posix_timers.c#L78
This one contains some places (like in the function “check_itimer”)
where the error detection and corresponding exception handling is incomplete
so far.
Other source files can contain similar update candidates.
There are different design options available to improve the software
situation here.
Which development directions do you prefer?
Regards,
Markus
prev parent reply other threads:[~2017-11-21 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 14:04 selftests: Completion of error handling SF Markus Elfring
2017-11-21 15:40 ` Shuah Khan
2017-11-21 19:30 ` 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=dc266850-52d0-8380-7ab1-087c07a709fb@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).