From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 3 Oct 2018 11:06:33 +0100 From: Sudeep Holla To: Mauro Carvalho Chehab Message-ID: <20181003100633.GB12570@e107155-lin> References: <20181001140402.0799a8f0@gandalf.local.home> <20181002011856.GA10841@kroah.com> <20181002090713.71b529fe@gandalf.local.home> <20181002161730.GA7119@kroah.com> <20181002163001.GA11068@kroah.com> <20181002183743.78eac32d@coco.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181002183743.78eac32d@coco.lan> Cc: Greg Kroah-Hartman , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Oct 02, 2018 at 06:37:43PM -0300, Mauro Carvalho Chehab wrote: [...] > > Even if it won't be possible to crash the Kernel or escalate > privileges, I suspect that several stuff in debugfs should never > be enabled on production systems, as they may reveal things like > memory addresses and other stuff that could be used to help someone > to crack a system. > I completely agree with that. Recently I reviewed patches to support power management on some ARM platforms which had complete system clock control in debugfs. It even had access to many system controls that it can send to remote system control processor which we really don't want in production systems. -- Regards, Sudeep