Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp4530529pxb; Tue, 25 Jan 2022 12:24:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJyUzCNLH8VZOT/4BLtlqpJqCcq95XKD2R6Dg5lVkfAo4u4LnKcF/7fk/uza+LkNf0i0G9DG X-Received: by 2002:a17:902:70c7:b0:149:d966:789d with SMTP id l7-20020a17090270c700b00149d966789dmr20325377plt.164.1643142246651; Tue, 25 Jan 2022 12:24:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643142246; cv=none; d=google.com; s=arc-20160816; b=Op447l9LKeBzlg2RduMPHu0SXS0A1E0syAHK/kihJCYqb0UDo4Q6yVP2wWM7VTq0Qy 7D8CHzza/oWxUWKFaAC2JlcK/hPemOdT/R2q+9EHQaxApBe97w9qjDA6zVe6I7q8qhN5 1jsh+GlK2mBe2ARTkfOfESEpRB0v4nKyPuyKKVLOnnMsDVNl4MCQslQ2h6qpQj9JbXiX w3kF0ETcEAeo9mRGFsmNFfTAXJiKi6p94LyTSN9tL0V4Uq/JRbKO1eeGRdHkkKmLR3KU V2eC0DYkglc2ONc5j4ZpO457ZkreHVrlbBXgUzajQyOnMSguYtd90qWPeTc/7x+k/Ywv eYEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=Dn1h+h//7C7r0CMp9MBF8PsBHihiUtbwCxlNVYgOqIw=; b=wCgduDdHAX2MPKlVkjIkfqE7f1ySZvYbZALpES9yNYZNuXxzWwpBB3keb3HjFWbXsH hJxujjE3oFM9TMORxA10duolrgx6d3NmQ78oM0QMhBskaebuaUJyJZLsTuLG/ZsmyppZ qyNDGI8YSf+gZRQRBU4hdIjaRLLktRlUtGIv0ch3WhTXzwq+eblT5wjNlwAb3n4kgXT6 nHcrVMU0EnPOtJtiQs12IDWZCmYi4BU5lYl1yaPJy4lwwKNV0NqRxBQaN72XB3KM64dO arYwBGSDszD7fenGKQ62zeErcdHO1ZYs9LFeqiCe299OxLnM1bVdsThQ/VL4cyasA4UP 8clQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q7si15667717pfs.215.2022.01.25.12.23.49; Tue, 25 Jan 2022 12:24:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1580156AbiAYOmf (ORCPT + 99 others); Tue, 25 Jan 2022 09:42:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1579776AbiAYOiw (ORCPT ); Tue, 25 Jan 2022 09:38:52 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 478D4C061401; Tue, 25 Jan 2022 06:38:51 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 0EB82B81812; Tue, 25 Jan 2022 14:38:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 22EE7C340E0; Tue, 25 Jan 2022 14:38:48 +0000 (UTC) Date: Tue, 25 Jan 2022 09:38:46 -0500 From: Steven Rostedt To: Yang Shi Cc: Cong Wang , linux-block@vger.kernel.org, Linux Kernel Mailing List , Jens Axboe Subject: Re: [Patch v3] block: introduce block_rq_error tracepoint Message-ID: <20220125093846.59826cad@gandalf.local.home> In-Reply-To: <20220125093702.3ffdb721@gandalf.local.home> References: <20200203053650.8923-1-xiyou.wangcong@gmail.com> <20220125093702.3ffdb721@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 25 Jan 2022 09:37:02 -0500 Steven Rostedt wrote: > > > +TRACE_EVENT(block_rq_error, > > > + > > > + TP_PROTO(struct request *rq, int error, unsigned int nr_bytes), > > > + > > > + TP_ARGS(rq, error, nr_bytes), > > > + > > > + TP_STRUCT__entry( > > > + __field( dev_t, dev ) > > > + __string( name, rq->rq_disk ? rq->rq_disk->disk_name : "?") > > > + __field( sector_t, sector ) > > > + __field( unsigned int, nr_sector ) > > > + __field( int, error ) > > > + __array( char, rwbs, RWBS_LEN ) > > Why is the above not "__string" ? > > > > + ), > > > + > > > + TP_fast_assign( > > > + __entry->dev = rq->rq_disk ? disk_devt(rq->rq_disk) : 0; > > > + __assign_str(name, rq->rq_disk ? rq->rq_disk->disk_name : "?"); > > __assign_str() will not work on an __array() type. It only works here > because you added it at the end, but it's just shear luck that it didn't > crash. Never mind :-p I see the above is for name which is __string, and the array is for rwbs which is filled below. I need to finish my first cup of coffee before reviewing patches. -- Steve > > > > > + __entry->sector = blk_rq_pos(rq); > > > + __entry->nr_sector = nr_bytes >> 9; > > > + __entry->error = error; > > > + > > > + blk_fill_rwbs(__entry->rwbs, rq->cmd_flags, nr_bytes); > > > + ), > > > + > > > + TP_printk("%d,%d %s %s %llu + %u [%d]", > > > + MAJOR(__entry->dev), MINOR(__entry->dev), > > > + __get_str(name), __entry->rwbs, > > > + (unsigned long long)__entry->sector, > > > + __entry->nr_sector, __entry->error) > > > +); > > > +