Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1471424ybt; Mon, 15 Jun 2020 00:45:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwFL6l1Zl2dgmhtGJ29U95RrcBHSI7fe+NllgNRGNp6VlvH7lhezHJRSMQGENsFdmYP56jK X-Received: by 2002:a17:906:b59:: with SMTP id v25mr25365300ejg.114.1592207153934; Mon, 15 Jun 2020 00:45:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592207153; cv=none; d=google.com; s=arc-20160816; b=he+FNtfFYsGlKHGUSbx/1xUKAcGYqSdKwtC0KgvfpBXM+nkvWft1remclZHi6BAEIC 6WyYicS8HVIx/aZi2+jAA5+fasYFuIpEXNC7IDjq7Zp5fKWiSzRFO62CdiGZGFfbJ1ac cY76z2dCsbkto+SsrTpVFXmE4VNVZW6AbrZRFbMJs823n+dFnciX4W9Ny5atsAjwPch2 PxvvgfrXer1Iy/mR002VrUv18CrNDSffVfrn2xDR3OgjafuQ4hjo4yqS+//55S0oedmJ R43C9frvdG7L6/5qakX5kZAWaA/CPtTAB4re7FKEGZR5sN/DnCQsk0XY2r014uZJ7VwY I5YQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=lIKplq6OxAw/ogQU3l1JmMLGkL/923KhF0C4cNkhxFU=; b=BZd6KYZV7+FRT0nBiKDsPTB8qzvpnaj1qt7ypyaUSM0jC465o6fx60ESJ1vo9iojWV DliSQQZtDpQW2kQ1Tr8sLkued9X4KePQ6Ovzjt8j44EJL09la2XDrmOvBDTrrgMK7r0Y 4d5IlAvKuFqLN7uso42M89JgxuDQU7GDCep9ipq4Izmuag1BnRocInEzjsd7tegmZ5+k jXSSIIW8xp9Vw3v6CC17U11g+IfzxhI1g4njFsaWhLlzJfRjiEoxpTH2YrCKi31+SMrP K0PfyckE9z2KurSpWbwoxmcBGaJ75OpX5VihWOJun4oPo8TbDch+Behi/HquqNHM3Gwo a1tg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o18si7899157ejb.193.2020.06.15.00.45.31; Mon, 15 Jun 2020 00:45:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728593AbgFOHnS (ORCPT + 99 others); Mon, 15 Jun 2020 03:43:18 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:5827 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728260AbgFOHnS (ORCPT ); Mon, 15 Jun 2020 03:43:18 -0400 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 3F70A45BD575FDFD01CC; Mon, 15 Jun 2020 15:43:13 +0800 (CST) Received: from [127.0.0.1] (10.166.213.7) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.487.0; Mon, 15 Jun 2020 15:43:09 +0800 Subject: Re: [PATCH] erofs: Eliminate usage of uninitialized_var() macro To: Gao Xiang CC: , , , , , Kees Cook , References: <20200615040141.3627746-1-yanaijie@huawei.com> <20200615072521.GA25317@xiangao.remote.csb> From: Jason Yan Message-ID: <783fe4f9-fb1f-7f5e-c900-7e30d5c85222@huawei.com> Date: Mon, 15 Jun 2020 15:43:09 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: <20200615072521.GA25317@xiangao.remote.csb> Content-Type: text/plain; charset="gbk"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.166.213.7] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ?? 2020/6/15 15:25, Gao Xiang ะด??: > Hi Jason, > > On Mon, Jun 15, 2020 at 12:01:41PM +0800, Jason Yan wrote: >> This is an effort to eliminate the uninitialized_var() macro[1]. >> >> The use of this macro is the wrong solution because it forces off ANY >> analysis by the compiler for a given variable. It even masks "unused >> variable" warnings. >> >> Quoted from Linus[2]: >> >> "It's a horrible thing to use, in that it adds extra cruft to the >> source code, and then shuts up a compiler warning (even the _reliable_ >> warnings from gcc)." >> >> The gcc option "-Wmaybe-uninitialized" has been disabled and this change >> will not produce any warnnings even with "make W=1". >> >> [1] https://github.com/KSPP/linux/issues/81 >> [2] https://lore.kernel.org/lkml/CA+55aFz2500WfbKXAx8s67wrm9=yVJu65TpLgN_ybYNv0VEOKA@mail.gmail.com/ >> >> Cc: Kees Cook >> Cc: Chao Yu >> Signed-off-by: Jason Yan >> --- > > I'm fine with the patch since "-Wmaybe-uninitialized" has been disabled and > I've also asked Kees for it in private previously. > > I still remembered that Kees sent out a treewide patch. Sorry about that > I don't catch up it... But what is wrong with the original patchset? > Yes, Kees has remind me of that and I will let him handle it. So you can ignore this patch. Thanks, Jason > Thanks, > Gao Xiang > > > . >