All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Lichota <krzysiek@lichota.net>
To: linux-btrace@vger.kernel.org
Subject: blktrace crashing with 2.6.22-rc3
Date: Tue, 12 Jun 2007 10:15:02 +0000	[thread overview]
Message-ID: <466E7226.7060609@lichota.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hello!
I am trying to use blktrace on latest Ubuntu kernel for Gutsy
(2.6.22-rc3, git tree is at
git://kernel.ubuntu.com/ubuntu/ubuntu-gutsy.git and web frontend at
http://kernel.ubuntu.com/git).

I have compiled it with blktrace enabled and when I try to run
blktrace -k to stop tracing, it doesn't do anything, but in dmesg I can
see the messages:
[  239.499614] DebugFS rmdir on hda failed : directory not empty.
[  239.499637] DebugFS rmdir on block failed : directory not empty.

If I try to kill it afterwards using ^C, it shows message "BLKTRACESTOP:
invalid argument", crashes with segmentation fault (core file is empty)
and I cannot start it again.

This happens if I run blktrace using: blktrace -d /dev/hda -o somefile
(on the same partition which is traced).

If I use network mode, it works fine.

blktrace tools are pulled today using git:
$ cat .git/remotes/origin
URL: git://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git
Pull: refs/heads/master:refs/heads/origin

Should I investigate it further or is it a known issue?

Regards

	Krzysztof Lichota



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

             reply	other threads:[~2007-06-12 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 10:15 Krzysztof Lichota [this message]
2007-06-12 10:39 ` blktrace crashing with 2.6.22-rc3 Jens Axboe
2007-06-12 15:10 ` Krzysztof Lichota
2007-06-12 16:23 ` Jens Axboe
2007-07-11 12:48 ` Jens Axboe

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=466E7226.7060609@lichota.net \
    --to=krzysiek@lichota.net \
    --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 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.