Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     rostedt@goodmis.org, mhiramat@kernel.org, acme@redhat.com,
        mingo@elte.hu, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org, Yang Jihong <yangjihong1@huawei.com>
In-Reply-To: <20221122040410.85113-1-yangjihong1@huawei.com>
References: <20221122040410.85113-1-yangjihong1@huawei.com>
Subject: Re: [PATCH] blktrace: Fix output non-blktrace event when blk_classic
 option enabled
Message-Id: <167051682259.135565.3126267294037734458.b4-ty@kernel.dk>
Date:   Thu, 08 Dec 2022 09:27:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


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