[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167051682259.135565.3126267294037734458.b4-ty@kernel.dk>
Date: Thu, 08 Dec 2022 09:27:02 -0700
From: Jens Axboe <axboe@...nel.dk>
To: rostedt@...dmis.org, mhiramat@...nel.org, acme@...hat.com,
mingo@...e.hu, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, Yang Jihong <yangjihong1@...wei.com>
Subject: Re: [PATCH] blktrace: Fix output non-blktrace event when blk_classic
option enabled
On Tue, 22 Nov 2022 12:04:10 +0800, Yang Jihong wrote:
> When the blk_classic option is enabled, non-blktrace events must be
> filtered out. Otherwise, events of other types are output in the blktrace
> classic format, which is unexpected.
>
> The problem can be triggered in the following ways:
>
> # echo 1 > /sys/kernel/debug/tracing/options/blk_classic
> # echo 1 > /sys/kernel/debug/tracing/events/enable
> # echo blk > /sys/kernel/debug/tracing/current_tracer
> # cat /sys/kernel/debug/tracing/trace_pipe
>
> [...]
Applied, thanks!
[1/1] blktrace: Fix output non-blktrace event when blk_classic option enabled
commit: f596da3efaf4130ff61cd029558845808df9bf99
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists