All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Greg Banks <gnb@melbourne.sgi.com>, greg@kroah.com
Cc: linux-kernel@vger.kernel.org, nfsv4@linux-nfs.org,
	systemtap@sources.redhat.com
Subject: Re: [Patch 0/2] dynamic debug
Date: Fri, 6 Feb 2009 11:28:43 -0500	[thread overview]
Message-ID: <20090206162843.GA3397@redhat.com> (raw)
In-Reply-To: <498B9852.5060909@melbourne.sgi.com>

On Fri, Feb 06, 2009 at 12:54:26PM +1100, Greg Banks wrote:
> > ok, patch below resolves the space issue.
> >   
> 
> The above patch makes the output much easier for a human to read, which
> is good.
> 
> However it's half the job.  The parser for the language used when
> writing to the control file still uses whitespace to tokenize and is
> still too dumb to handle quoting and so needs all whitespace escaped,
> like this
> 
> #echo -n 'format Setting\040node\040for\040non-present\040cpu +p' > /mnt/debugfs/dynamic_debug/control
> 
> Which is documented in the howto.  So that you could copy-n-paste in a
> terminal window, I chose to make the input and output formats as similar
> as possible, and used escaping for all whitespace on output.  That was
> just me being lazy, sorry.  Below is a patch which implements a better
> solution, which is to fix ddebug_tokenize() to handle simple quoting so
> the above would look like
> 
> #echo -n 'format "Setting node for non-present cpu" +p' > /mnt/debugfs/dynamic_debug/control
> 
> 

agreed. patch looks good...and I've tested it.

Greg KH, to be clear, Greg Banks patch applies on top of the additional
patch which I sent.

thanks,

-Jason

      reply	other threads:[~2009-02-06 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 16:45 [Patch 0/2] dynamic debug Jason Baron
2009-02-05 17:58 ` Greg KH
2009-02-05 18:43   ` Jason Baron
2009-02-06  1:13     ` Greg KH
2009-02-06  1:54     ` Greg Banks
2009-02-06 16:28       ` Jason Baron [this message]

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=20090206162843.GA3397@redhat.com \
    --to=jbaron@redhat.com \
    --cc=gnb@melbourne.sgi.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=systemtap@sources.redhat.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.