Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp3542526ybk; Tue, 19 May 2020 07:13:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyt/bgp3G0kqBk/gKOdK+KzjB2aPSggZ5VOjNaQrZlcBSicrh03t4i7DIRoNOaJ8rEBIbfm X-Received: by 2002:a50:e1c5:: with SMTP id m5mr12422730edl.47.1589897609178; Tue, 19 May 2020 07:13:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589897609; cv=none; d=google.com; s=arc-20160816; b=q5+I/gmBAJur5JGOdo4UvDdTFBxUHyyV0nh9NLVSZ1VkVttukX3e0IhqsaFy/vS2fb EDy6lw7LxKb8zHcVlFJ36DEVU8cOxVOj3ipOo51DdMOXGizUEITW/yfqE5rfVcovjZhl NRK7+erzpw7Yx3OWpiZsUeE0ox9jFngysD9/LwwEp9psKP/m7SqBWbRoedn3KLL3yTV4 2wPZpRy0nxVMrW7HzD8XoNloMPdNMcg9klHoo4on1vR5rVfpLCTS1RNvK1QZaejK4Mo8 9e6ErhQCwUhbV9bkPCfMEkhBm2h+U3QaCW75AmVXZPrsm0HyDDFpY5qF3K++T4zwU6RO ys0w== 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=aFSR4hvLKUk9QGeYT8aBSJS9SBQSkMFJclKyFWePE8o=; b=An3eLsvfoldceK76m+M9Q/mT4yE/7CA96FI7pWxlRfTC5QxXw63OM08sT+ZifbnxlV 3zOyMo89V/HAM5agmMmHS0wbx/k8EnJfnVwghfzL/2JnwVK0GXaCyBb/R51e4Qjm9xZJ vpFVoINsTwAGFv7zvmGRGBvHKyQkn0gzKRpS2Nvj6OvVLlvOWKN0aXb/c4Koao1MO9zw 9VLrZ8/Na9iEPbYxMLGU3LBro1dYOEj1lZiIkfagZ5QuSsjGJWrvlLfYzOlQ5kGra4bc uNoM+7WFh6HpKMluAsMmUrjbPkT1lr6a8l06bLBa8VY46qUGdARcUV6bS91AUELhjfEY gU/g== 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 bu28si809152edb.189.2020.05.19.07.13.04; Tue, 19 May 2020 07:13:29 -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 S1728973AbgESOLU (ORCPT + 99 others); Tue, 19 May 2020 10:11:20 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:4816 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727057AbgESOLU (ORCPT ); Tue, 19 May 2020 10:11:20 -0400 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id DA756E8C56956D7A7E34; Tue, 19 May 2020 22:11:17 +0800 (CST) Received: from [10.166.215.145] (10.166.215.145) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.487.0; Tue, 19 May 2020 22:11:12 +0800 Subject: Re: [PATCH v2] kdb: Make the internal env 'KDBFLAGS' undefinable To: Daniel Thompson CC: Doug Anderson , Jason Wessel , Masahiro Yamada , , LKML References: <20200516092606.41576-1-liwei391@huawei.com> <20200519114008.lmdf44zmgcmnf27c@holly.lan> From: "liwei (GF)" Message-ID: Date: Tue, 19 May 2020 22:11:11 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <20200519114008.lmdf44zmgcmnf27c@holly.lan> Content-Type: text/plain; charset="gbk" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.166.215.145] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On 2020/5/19 19:40, Daniel Thompson wrote: > On Sat, May 16, 2020 at 05:26:06PM +0800, Wei Li wrote: >> 'KDBFLAGS' is an internal variable of kdb, it is combined by 'KDBDEBUG' >> and state flags. But the user can define an environment variable named >> 'KDBFLAGS' too, so let's make it undefinable to avoid confusion. >> >> Signed-off-by: Wei Li >> Reviewed-by: Douglas Anderson > > I took a quick look at this and find myself thinking of KDBFLAGS as > something of a misfeature. > > I think I'd rather get kdb_env to show the value we wrote into > KDBDEBUG. > > Sure this means we cannot use KDBDEBUG to look at the least significant > 16-bits but I think anyone who is debugging kdb itself should know > enough to use `md4c1 kdb_flags` to read those anyway. > > Agree. That will be more clear with no confusion. Currently, KDBFLAGS will be shown only when KDBDEBUG is set, that is weird too. So, let's just make it simple. I can fix it as you suggested in the next post. Thanks, Wei