Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp225248ybl; Wed, 4 Dec 2019 01:30:56 -0800 (PST) X-Google-Smtp-Source: APXvYqyDKZdNQ3tV7pLg8PJZHqk19F2drxUvXQd3mBAvha7hVK+lt+0XjnqWvFa5PV1HRHf4RVwj X-Received: by 2002:a9d:3af:: with SMTP id f44mr1677715otf.332.1575451856467; Wed, 04 Dec 2019 01:30:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575451856; cv=none; d=google.com; s=arc-20160816; b=M3W+JV6frsxfhyDNr5ChfD/8W4UYdS3l2frCSD6VQlxvS+N35CtN7K/j4vJmgBmiVe YkKvTKlgW7APb65/0TRM342rodnU6DifpZP3HWieGR0HBdav8Bcey9vpAIbTyqXMlhUX 2lp505dQjd28mqWEgNW1oDaj3NpucXbQrFiGD14FmumoDpvLoVWscxpaUzA+CpAt9S6j 244cAp07AfvmsElZDNBkUPq5AV8eoyFL8iNlW6tR8GEjlcOb3URbylBcncjEGG9DVkt1 X63pqCkwXLPxEJt1bJnNFUWejb0eDdN4SKaIZ5KpSNIzCy/NHqFjKwiHaWrgA8ZQflpF Pnow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=42b3wPjQqJrEihMAe6qIDquU5tPC4DrlAz1S24UIuO8=; b=yPA1tQOj/6Eah/fi4ViwSbua6PwHzVndTLetHOQVR3zo7wQ8a1dT9mBIp2SNiAvQSf 8pkvQC9H1QsP/aSvyjNtjkyKe+3vUGHxaL+uCtnqNBF8l1BGpGJzgNRrM6KYF1u2dPuZ nxGmZ6h7IXzcss9sYMY+vuFUyaP0V5+bRbV7TfaW2TxTq7HuB9v49hnoEI3asx8emKOd 2QGGzWFE6Geeq9AcmuT4iR4o3uM1rmkSOad1tA03jO+plsB2csLNr6MBAjqlmYwHVSR3 NefWJSYlkH20Yv+5RvjogcCgxSFxXJi8D2LBIeEEMykZHHcy/b5KGUbsJM0MGUbqr1La kKWQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=RgpthHgQ; 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 q3si2834212otk.64.2019.12.04.01.30.43; Wed, 04 Dec 2019 01:30:56 -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; dkim=pass header.i=@kernel.org header.s=default header.b=RgpthHgQ; 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 S1727351AbfLDJ3q (ORCPT + 99 others); Wed, 4 Dec 2019 04:29:46 -0500 Received: from mail.kernel.org ([198.145.29.99]:52358 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725922AbfLDJ3q (ORCPT ); Wed, 4 Dec 2019 04:29:46 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7A18820675; Wed, 4 Dec 2019 09:29:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575451785; bh=olCGYBNqUiviVWQIvUISVF1ya1mFuGUwBKcuWe02w5A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RgpthHgQ4pZiPs1SeA4WN16ryXE8z7kGsS2Nfg7w3eSzy8phuZ/jczqJAkJdcoh+F dNfVPuA/3+EK+uS6fT4q+QMRDTKv7tQHPYYUkBX1K8f+C/22B1TPZB+KsJZCePobXH KmL81FjgHZO/PVDLHr4aRz1gYeqf8G+PSYwxrK6g= Date: Wed, 4 Dec 2019 10:29:42 +0100 From: Greg Kroah-Hartman To: Guoheyi Cc: Mike Waychison , linux-kernel@vger.kernel.org, wanghaibin 00208455 , Thomas Gleixner Subject: Re: firmware: dmi-sysfs: why is the access mode of dmi sysfs entries restricted to 0400? Message-ID: <20191204092942.GA3557583@kroah.com> References: <42bb2db8-66e0-3df4-75b7-98b2b2bcfca8@huawei.com> <20191204074133.GA3548765@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 04, 2019 at 05:01:06PM +0800, Guoheyi wrote: > > 在 2019/12/4 15:41, Greg Kroah-Hartman 写道: > > On Wed, Dec 04, 2019 at 03:31:22PM +0800, Guoheyi wrote: > > > 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? > > There's lots of "interesting" information in dmi entries that you > > probably do not want all processes reading, which is why they are > > restricted. > > > > > We would like to fetch CPU information from non-root application, is there > > > feasible way to do that? > > What specific CPU information is not currently exported in /proc/cpuinfo > > that only shows up in DMI entries that you are interested in? > > We'd like to get processor manufacturer, speed and version, and pass the > information to qemu virtual machine, for users of VM might be happy to see > this instead of "unknown xxx", while qemu may run as non-root. Careful about this as if you move that virtual machine around, those values will change and if userspace was depending on them being static (set up at program start time), then you might have problems. good luck! greg k-h