From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762706AbZENAeQ (ORCPT ); Wed, 13 May 2009 20:34:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762225AbZENAd6 (ORCPT ); Wed, 13 May 2009 20:33:58 -0400 Received: from TYO202.gate.nec.co.jp ([202.32.8.206]:54332 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761049AbZENAd5 (ORCPT ); Wed, 13 May 2009 20:33:57 -0400 Message-ID: <4A0B64AC.7010908@ct.jp.nec.com> Date: Thu, 14 May 2009 09:24:12 +0900 From: Hiroshi Shimamoto User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: "H. Peter Anvin" CC: Ingo Molnar , Subrata Modak , x86@kernel.org, Sachin P Sant , Andi Kleen , Andi Kleen , Linux Kernel , Balbir Singh , Thomas Gleixner , Ingo Molnar Subject: Re: [PATCH] Fix Warnining in arch/x86/kernel/signal.c References: <20090512155637.19380.9114.sendpatchset@subratamodak.linux.ibm.com> <4A0A2E57.7080709@ct.jp.nec.com> <1242205601.6325.15.camel@subratamodak.linux.ibm.com> <20090513135325.GA10434@elte.hu> <4A0B2C27.5020101@zytor.com> In-Reply-To: <4A0B2C27.5020101@zytor.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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