linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [patch 4/5] blktrace: disable kill option
Date: Tue, 20 Apr 2010 07:50:45 +0000	[thread overview]
Message-ID: <20100420075045.GD27497@kernel.dk> (raw)
In-Reply-To: <4B27CBD6.6060807@redhat.com>

On Tue, Dec 15 2009, Edward Shishkin wrote:
>

> Fixup for 513950.
> 
> Problem:
> 'blktrace -d <device> -k' does not kill a running
> backgound trace. Executing 'blktrace -d <device> -k'
> for the second time results in "BLKTRACETEARDOWN:
> Invalid argument" message and then each run of
> blktrace on that machine prints the following output:
> BLKTRACESETUP: No such file or directory.
> 
> The bug:
> The option -k results in clobbering information
> about running trace by kernel (blk_trace_remove),
> while resources (files open in debugfs by the running
> background blktrace) are not released.
> 
> Solution:
> . Disable non-working "kill" option;
> . Update documentation, advise to send SIGINT signal
>   via kill(1) to the running background blktrace for
>   its correct termination.

Patch does not compile:

gcc -o blktrace.o -c -Wall -O2 -g -W -D_GNU_SOURCE -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITSd blktrace.c
blktrace.c:446: error: stray ?#? in program
blktrace.c:453: error: expected ?,? or ?;? before ?if?
blktrace.c:454: error: stray ?#? in program
make: *** [blktrace.o] Error 1


        "\t-D Directory to prepend to output file names\n" \
#if KILL_OPT_ENABLED
        "\t-k Kill a running trace\n" \
#endif /* KILL_OPT_ENABLED */
        "\t-w Stop after defined time, in seconds\n" \


-- 
Jens Axboe


  reply	other threads:[~2010-04-20  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 17:48 [patch 4/5] blktrace: disable kill option Edward Shishkin
2010-04-20  7:50 ` Jens Axboe [this message]
2010-04-20 13:27 ` Edward Shishkin

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=20100420075045.GD27497@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).