Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp138183ybl; Tue, 3 Dec 2019 23:32:40 -0800 (PST) X-Google-Smtp-Source: APXvYqy0qvz7i/SbmNj8bJQoVLNQZp/aDLvEpaADrxRw9ZxlmoCjmqL30pWGPK/m4Ot49AjQNYP5 X-Received: by 2002:aca:782:: with SMTP id 124mr1382333oih.47.1575444760113; Tue, 03 Dec 2019 23:32:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575444760; cv=none; d=google.com; s=arc-20160816; b=vGmB0d6TzIc0NJbxezTsQMJhfDlhz6yCBn94KVZCqB2Ep5a+qIBUY9CN0ZLQvTnXXr xtJJN2Y5C/M2U1ZrjZwCdoEoQsU+e3duDdSJo4pL5CbDsQpTXx0fZFNnoio1yiyT1+t/ e29yl/sDZbYeWgjJ2D3B5NUdHQ5qebXYuaPgG+PbWWdhai9QkhmHm03dv7QWdzke4jlp OusPaTtnLSS6JRD3dCFwoT2RYdv5Mx4mJWOorsAz3tTZyrLtrdJy3FeMLEuTYG2fbXaQ bW8uvNMr4iDS/nwC4ADPBBBRN8kvOOXtqXnP+25NduPgCm8J8jshUJFHaXQlbKlACpSD GIkg== 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:mime-version :user-agent:date:message-id:subject:from:cc:to; bh=DjjhuEym3/Ms5q30mvK82p03BUtDI/YZUdXAxmB7R8c=; b=nBQaBlZynH7ZvLjr8MYghQE2kPZ7ow5P4BG4l3FXwQQVAFMA30eg7SPPSZrYFBJ2BB aM5cy4tDXJOSucMlCqVx6Wgwj6/XruK4DfQl8+D/b9zQTieDY8R4c4bT5cb7C693hREv BvrGPrLWe3+JhlxDDnpECudCMfVVE3aQ69c0HwPfShYSorkOROQP4eui98RoNR77O+eb Tuep1pFP9G7of7oiWi6PWkWvCAl6k8+Rrp7WendzGsHCSJzBOFdnXXguDHQKyOIwurFH cB8WrtdYkIAGGr9IlFz3UrT2bKcwtUEQl6EYW4bYlHh9TktOCezoNIdjd5M5vJkfjtXZ dd7g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y186si2778610oig.241.2019.12.03.23.32.26; Tue, 03 Dec 2019 23:32:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727127AbfLDHbb (ORCPT + 99 others); Wed, 4 Dec 2019 02:31:31 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:6747 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725958AbfLDHbb (ORCPT ); Wed, 4 Dec 2019 02:31:31 -0500 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 3F60F3216FAD16662644; Wed, 4 Dec 2019 15:31:30 +0800 (CST) Received: from [127.0.0.1] (10.133.216.73) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.439.0; Wed, 4 Dec 2019 15:31:23 +0800 To: Mike Waychison CC: , wanghaibin 00208455 , Thomas Gleixner , "Greg Kroah-Hartman" From: Guoheyi Subject: firmware: dmi-sysfs: why is the access mode of dmi sysfs entries restricted to 0400? Message-ID: <42bb2db8-66e0-3df4-75b7-98b2b2bcfca8@huawei.com> Date: Wed, 4 Dec 2019 15:31:22 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset="gbk"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.133.216.73] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Why is the access mode of dmi sysfs entries restricted to 0400? Is it for security concern? If it is, which information do we consider as privacy? We would like to fetch CPU information from non-root application, is there feasible way to do that? Any advice is appreciated. Thanks, Heyi