From: Chen Gang <gang.chen@asianux.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATH v4] itimers: Remove bogus NULL pointer check in sys_getitimer()
Date: Mon, 22 Jul 2013 10:45:21 +0800 [thread overview]
Message-ID: <51EC9CC1.1040304@asianux.com> (raw)
In-Reply-To: <51D62147.3000900@asianux.com>
Hello Maintainers:
Please help check this patch, when you have time.
Thanks.
On 07/05/2013 09:28 AM, Chen Gang wrote:
> Hello Maintainers:
>
> Is this patch under the normal work flow (or I should need a little more
> patience) ?
>
> Thanks.
>
> On 06/25/2013 09:16 AM, Chen Gang wrote:
>> People might be tricked into assuming that the return value for a
>> failed NULL pointer check should be -EINVAL instead of -EFAULT.
>>
>> Remove the misleading NULL pointer check to fix this nuisance.
>>
>> Aside of that this patch fixes the problem of NOMMU kernels, where
>> a NULL pointer dereference is a valid operation. This allows to
>> boot NOMMU kernels without working around the shortcomings of the
>> getitimer() system call, which have been ignored since this NULL
>> pointer check was introduced in Linux 0.96a.
>>
>> Signed-off-by: Chen Gang <gang.chen@asianux.com>
>> ---
>> kernel/itimer.c | 13 ++++++-------
>> 1 files changed, 6 insertions(+), 7 deletions(-)
>>
>> diff --git a/kernel/itimer.c b/kernel/itimer.c
>> index 8d262b4..3b12271 100644
>> --- a/kernel/itimer.c
>> +++ b/kernel/itimer.c
>> @@ -102,15 +102,14 @@ int do_getitimer(int which, struct itimerval *value)
>>
>> SYSCALL_DEFINE2(getitimer, int, which, struct itimerval __user *, value)
>> {
>> - int error = -EFAULT;
>> + int error;
>> struct itimerval get_buffer;
>>
>> - if (value) {
>> - error = do_getitimer(which, &get_buffer);
>> - if (!error &&
>> - copy_to_user(value, &get_buffer, sizeof(get_buffer)))
>> - error = -EFAULT;
>> - }
>> + error = do_getitimer(which, &get_buffer);
>> + if (!error &&
>> + copy_to_user(value, &get_buffer, sizeof(get_buffer)))
>> + error = -EFAULT;
>> +
>> return error;
>> }
>>
>>
>
>
--
Chen Gang
prev parent reply other threads:[~2013-07-22 2:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 11:26 [PATCH v2] kernel/itimer.c: beautify code, not need check 'value', so save one instruction, simpler and easier for readers Chen Gang
2013-06-20 12:02 ` Chen Gang
2013-06-20 12:55 ` Thomas Gleixner
2013-06-21 1:24 ` Chen Gang
2013-06-20 13:42 ` Thomas Gleixner
2013-06-21 2:04 ` Chen Gang
2013-06-21 10:31 ` [PATCH v3] kernel/itimer.c: remove the checking 'value' statement Chen Gang
2013-06-24 23:28 ` [PATCH v2] kernel/itimer.c: beautify code, not need check 'value', so save one instruction, simpler and easier for readers.t Thomas Gleixner
2013-06-25 0:58 ` Chen Gang
2013-06-25 1:16 ` [PATH v4] itimers: Remove bogus NULL pointer check in sys_getitimer() Chen Gang
2013-07-05 1:28 ` Chen Gang
2013-07-22 2:45 ` Chen Gang [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=51EC9CC1.1040304@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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