From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sachin P Sant <sachinp@linux.vnet.ibm.com>,
Andi Kleen <ak@linux.intel.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Fix Warnining in arch/x86/kernel/signal.c
Date: Thu, 14 May 2009 16:38:33 +0900 [thread overview]
Message-ID: <4A0BCA79.4090006@ct.jp.nec.com> (raw)
In-Reply-To: <20090514063059.17737.43329.sendpatchset@subratamodak.linux.ibm.com>
Subrata Modak wrote:
> Hello Hiroshi-san,
Hi Subrata,
>
> On Thu, 2009-05-14 at 09:24 +0900, Hiroshi Shimamoto wrote:
> H. Peter Anvin wrote:
>>> Ingo Molnar wrote:
>>>>>>>
>>>>>>> if (!access_ok(VERIFY_READ, frame, sizeof(*frame)))
>>>>>>> goto badframe;
>>>>>>> - if (__get_user(set.sig[0], &frame->sc.oldmask) || (_NSIG_WORDS > 1
>>>>>>> - && __copy_from_user(&set.sig[1], &frame->extramask,
>>>>>>> - sizeof(frame->extramask))))
>>>>>>> +
>>>>>>> + if ( (__copy_from_user(&set.sig[1], &frame->extramask,
>>>>>>> + sizeof(frame->extramask)) && _NSIG_WORDS > 1) ||
>>>>>>> + __get_user(set.sig[0], &frame->sc.oldmask))
>>>>>>> goto badframe;
>>>>>> I'm not sure why this eliminates that warning.
>>>>>> set.sig[0] may not be initialized too, if __copy_from_user() failed.
>>>>> True, but only when either or both of __copy_from_user() and
>>>>> (_NSIG_WORDS > 1) fails. But in all instances set.sig[1] gets
>>>>> initialized.
>>>>>
>>>>>> I don't have enough time to look at this right now, sorry.
>>>>>>
>>>>>> Another question, __copy_from_user() will be called even if
>>>>>> _NSIG_WORDS is less than 2, perhaps it never occurs.
>>>>>> I think, to check _NSIG_WORDS > 1 before calling __copy_from_user()
>>>>>> is better.
>>>>> Fine. Let Ingo/Thomas/Peter decide whether they would like this fix or
>>>>> drop it.
>>>> If you get the Acked-by from Hiroshi-san it looks good to me. He
>>>> modified this code last.
>>>>
>>> This seriously looks wrong to me. If _NSIG_WORDS == 1, then calling
>>> __copy_from_user here is a serious error.
>> Right. If _NSIG_WORDS is 1, sigset_t set has only sig[0], writing to
>> set.sig[1] means stack corruption.
>>
>> Subrata, could you try like this?
>> if ((_NSIG_WORDS > 1 && __copy_from_user(&set.sig[1], ...) ||
>> __get_user(set.sig[0], ...))
>>
>>
>
> I tried out and the compiler does not complain in this case.
> Updated Patch below. Please review.
thanks for testing, it looks OK except small nits.
Could you please check with checkpatch.pl?
>
> Signed-Off-By: Subrata Modak <subrata@linux.vnet.ibm.com>
WARNING: Signed-off-by: is the preferred form
> To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
> Cc: H. Peter Anvin <hpa@zytor.com>,
> Cc: Ingo Molnar <mingo@elte.hu>,
> Cc: x86@kernel.org,
> Cc: Sachin P Sant <sachinp@linux.vnet.ibm.com>,
> Cc: Andi Kleen <andi@firstfloor.org>,
> Cc: Andi Kleen <ak@linux.intel.com>,
> Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
> Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
> Cc: Thomas Gleixner <tglx@linutronix.de>,
> Cc: Ingo Molnar <mingo@redhat.com>
> Subject: Re:[PATCH] Fix Warnining in arch/x86/kernel/signal.c
> ---
>
> --- a/arch/x86/kernel/signal.c 2009-05-14 11:27:15.000000000 +0530
> +++ b/arch/x86/kernel/signal.c 2009-05-14 11:50:52.000000000 +0530
> @@ -576,9 +576,9 @@ unsigned long sys_sigreturn(struct pt_re
>
> if (!access_ok(VERIFY_READ, frame, sizeof(*frame)))
> goto badframe;
> - if (__get_user(set.sig[0], &frame->sc.oldmask) || (_NSIG_WORDS > 1
> - && __copy_from_user(&set.sig[1], &frame->extramask,
> - sizeof(frame->extramask))))
> + if ( (_NSIG_WORDS > 1 && __copy_from_user(&set.sig[1],
ERROR: space prohibited after that open parenthesis '('
> + &frame->extramask, sizeof(frame->extramask))) ||
ERROR: code indent should use tabs where possible
> + __get_user(set.sig[0], &frame->sc.oldmask))
ERROR: code indent should use tabs where possible
Thanks,
Hiroshi
> goto badframe;
>
> sigdelsetmask(&set, ~_BLOCKABLE);
>
> ---
> Regards--
> Subrata
>
>> I wonder whether gcc really complains about the case of
>> __get_user(set.sig[0], ...) failure.
>> Why, the case which sig[0] initialized and sig[1] uninitialized is NG
>> and the case which sig[0] uninitialized and sig[1] initialized is OK.
>>
>> Thanks,
>> Hiroshi
>
next prev parent reply other threads:[~2009-05-14 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 6:30 Re:[PATCH] Fix Warnining in arch/x86/kernel/signal.c Subrata Modak
2009-05-14 7:38 ` Hiroshi Shimamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-14 9:12 Subrata Modak
2009-05-15 2:57 ` [PATCH] " Hiroshi Shimamoto
2009-05-15 3:32 ` Hiroshi Shimamoto
2009-05-15 10:16 ` Subrata Modak
2009-05-18 3:36 ` Hiroshi Shimamoto
2009-05-18 6:38 ` Subrata Modak
2009-05-12 15:56 Subrata Modak
2009-05-13 2:20 ` Hiroshi Shimamoto
2009-05-13 9:06 ` Subrata Modak
2009-05-13 13:53 ` Ingo Molnar
2009-05-13 20:23 ` H. Peter Anvin
2009-05-14 0:24 ` Hiroshi Shimamoto
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=4A0BCA79.4090006@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=subrata@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.