From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: blktrace crashing with 2.6.22-rc3
Date: Tue, 12 Jun 2007 16:23:06 +0000 [thread overview]
Message-ID: <20070612162306.GN18832@kernel.dk> (raw)
In-Reply-To: <466E7226.7060609@lichota.net>
On Tue, Jun 12 2007, Krzysztof Lichota wrote:
> Jens Axboe napisa??(a):
> >> Should I investigate it further or is it a known issue?
> >
> > I think it's a known issue. Don't run blktrace -k unless the trace is
> > really stuck - does it work correctly if you just ctrl-c out of
> > blktrace?
>
> Yes, it works. I just got the impression that blktrace -k is the
> preferred way of terminating the trace.
oh no, -k is for KILL, extremely unpolite :-)
> Thanks for help :)
It sounds like you have found a way to reliably cause that bug, so I'll
see if I can reproduce and get it fixed.
--
Jens Axboe
next prev parent reply other threads:[~2007-06-12 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 10:15 blktrace crashing with 2.6.22-rc3 Krzysztof Lichota
2007-06-12 10:39 ` Jens Axboe
2007-06-12 15:10 ` Krzysztof Lichota
2007-06-12 16:23 ` Jens Axboe [this message]
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=20070612162306.GN18832@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).