lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1252362420.2964.53.camel@localhost.localdomain>
Date:	Mon, 07 Sep 2009 18:27:00 -0400
From:	Steven Rostedt <srostedt@...hat.com>
To:	Greg KH <greg@...ah.com>
Cc:	Peter Zijlstra <peterz@...radead.org>, leemgs1@...il.com,
	linux-kernel <linux-kernel@...r.kernel.org>,
	mathieu.desnoyers@...ymtl.ca, Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 1/5] debugfs - Fix mount directory of debugfs by
 default in events.txt

On Mon, 2009-09-07 at 14:30 -0700, Greg KH wrote:

> > 
> > From what people tell me it wasn't a clear consensus.
> 
> Specifics please.

Well I still avoid it. I've been broken into telling people publicly to
mount it in /sys/kernel/debug, but I've never done it myself.

> 
> > > So what is the problem?
> > 
> > Its not related to sysfs in any way I can discover,
> 
> So, other filesystems are mounted in sysfs, and in /proc for many years.
> 
> > its not consistent with most of the other virtual fs',
> 
> What do you mean by this?
> 
> > and its way too much typing.
> 
> tab completion is your friend, as is environment variables.  Don't
> choose stuff just because you are lazy :)

/sy <tab> k <tab> d <tab>

   or

/deb <tab>

I like the second one much better.

> 
> > we don't mount /dev, /proc, /sys in weird places either, so why should
> > we mount /debug in a cumbersome location.
> 
> Because it is a _kernel_ debug thing, not a system-level debug thing.
> What would userspace developers think about /debug ?  Why would they
> care about such a thing?
> 
> As much as we tend to ignore it, kernel developers are not the primary,
> or only, users of Linux :)

Actually this is a very good point. I think that the tracing system has
matured beyond a "debug" level and is being enabled on production
systems. Both fedora and debian are now shipping kernels with it
enabled. Perhaps we should create another pseudo fs that can be like
debugfs but for stable ABIs. A new interface could start out in debugfs,
but when it has reached a stable interface, then it could be moved to
another location to signal this.

/proc has been criticized for the pollution of non process related
information. This happened because there was no place else to place it.
Then came /sys which was suppose to take over this, but IMHO, it is too
over-engineered and too complex to use (I still stumble over kobjects).
I found that debugfs was a nice and simple interface to use. What about
creating a new fs that works like debugfs but is for stable interfaces
and can be mounted at root?

   /kernel?


-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ