All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>, Greg KH <gregkh@suse.de>
Subject: Re: [ltt-dev] [PATCH 1/2] Make lttctl mount debugfs automatically
Date: Thu, 8 Jan 2009 22:30:22 -0500	[thread overview]
Message-ID: <20090109033021.GA25504@Krystal> (raw)
In-Reply-To: <7C0A417AB5B84CDCB9A9484C4E13A08C@zhaoleiwin>

* Zhaolei (zhaolei@cn.fujitsu.com) wrote:
> * From: "Mathieu Desnoyers" <compudj@krystal.dyndns.org>
> >* Zhaolei (zhaolei@cn.fujitsu.com) wrote:
> >> * From: "Pierre-Marc Fournier" <pierre-marc.fournier@polymtl.ca>
> >> > Zhaolei wrote:
> >> >> lttctl need debugfs mounted,
> >> >> This patch make lttctl mount debugfs automatically when it is not mounted.
> >> >> 
> >> > 
> >> > Isn't having a utility such as lttctl mount filesystems against standard
> >> > unix semantics? Can you give an example of another standard command that
> >> > uses a filesystem and that tries to mount it if it isn't already
> >> > mounted? 
> >> Hello, Pierre-Marc,
> >> 
> >> I can give a an example.
> >> It is SystemTap.
> >> 
> > 
> > No offence, but can you find an example which is not explicitly
> > described as "bad taste" example by many people in the Linux kernel
> > community ?
> Hello, Mathieu
> 
> I can't find another example of mounting debugfs automatically.
> Maybe it is because debugfs is not widely used as others such as sysfs and
> procfs.
> 
> sysfs and procfs are mounted in boot, and user-mode tools need not check and
> mount then again. But debugfs is not too useful for normal user who just use
> linux to edit text and browse internet, so mount debugfs in boot period is not
> a good idea.
> So, IMHO, debugfs's usage is not same as sysfs and procfs, we need not mount
> sysfs and procfs in user-mode program, but maybe it is different for debugfs.
> 
> On the other hand, I also understand your opinion, mount a fs in program looks
> strange(but can make user easy to use...), so you can feel free to ignore this
> patch.
> Same with [PATCH 2/2] Make lttctl load ltt-trace-control module automatically.
> 

I wonder what's Greg KH (and others) opinion about this ?

Mathieu


> Regards
> Zhaolei
> 
> > 
> > Mathieu
> > 
> >> Regards
> >> Zhaolei
> >> 
> >> > My guess is we should warn about the filesystem not being
> >> > mounted, but not try to call mount() directly.
> >> > 
> >> >> Little cleanup also done(combile 2 getdebugfsmntdir() into one).
> >> >> 
> >> >> Applies on top of ltt-control-0.63-03012009.
> >> >> 
> >> > 
> >> >
> >> _______________________________________________
> >> ltt-dev mailing list
> >> ltt-dev@lists.casi.polymtl.ca
> >> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> >> 
> > 
> > -- 
> > Mathieu Desnoyers
> > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> > 
> >
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

       reply	other threads:[~2009-01-09  3:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49646208.7070607@cn.fujitsu.com>
     [not found] ` <4964BA2B.30200@polymtl.ca>
     [not found]   ` <AA3F776E5F6246859F1978B7C7CF1919@zhaoleiwin>
     [not found]     ` <20090108144430.GA3778@Krystal>
     [not found]       ` <7C0A417AB5B84CDCB9A9484C4E13A08C@zhaoleiwin>
2009-01-09  3:30         ` Mathieu Desnoyers [this message]
2009-01-13 23:54           ` [ltt-dev] [PATCH 1/2] Make lttctl mount debugfs automatically Greg KH
2009-01-14  2:02             ` Josh Boyer
2009-01-14  5:16             ` Mathieu Desnoyers
2009-01-14  5:54               ` Greg KH
2009-01-15  1:41                 ` Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090109033021.GA25504@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=zhaolei@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.