archive mirror
 help / color / mirror / Atom feed
From: Steve French <>
To: "Ralph Böhme" <>
Cc: CIFS <>,
	LKML <>,
	samba-technical <>,
	linux-fsdevel <>
Subject: Re: [PATCHv2][SMB3] Add kernel trace support
Date: Fri, 18 May 2018 13:43:14 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20180518184630.axfa7oq4pewb7foj@kazak>

On Fri, May 18, 2018 at 11:46 AM, Ralph Böhme <> wrote:
> On Thu, May 17, 2018 at 09:36:36PM -0500, Steve French via samba-technical wrote:
>> Patch updated with additional tracepoint locations and some formatting
>> improvements. There are some obvious additional tracepoints that could
>> be added, but this should be a reasonable group to start with.
>> From edc02d6f9dc24963d510c7ef59067428d3b082d3 Mon Sep 17 00:00:00 2001
>> From: Steve French <>
>> Date: Thu, 17 May 2018 21:16:55 -0500
>> Subject: [PATCH] smb3: Add ftrace tracepoints for improved SMB3 debugging
>> Although dmesg logs and wireshark network traces can be
>> helpful, being able to dynamically enable/disable tracepoints
>> (in this case via the kernel ftrace mechanism) can also be
>> helpful in more quickly debugging problems, and more
>> selectively tracing the events related to the bug report.
>> This patch adds 12 ftrace tracepoints to cifs.ko for SMB3 events
>> in some obvious locations.  Subsequent patches will add more
>> as needed.
>> Example use:
>>    trace-cmd record -e cifs
>>    <run test case>
>>    trace-cmd show
> pardon my ignorance, but are these tracepoints usable with other tracing
> frameworks like Systemtap?
> Last time I checked, Systemtap looked like *the* tool. Is there a generic trace
> point infrastructure that tracing tools can consume, so we're not tied to
> ftrace?

At the kernel filesystem/mm summit a few recommended using ftrace
(trace-cmd).  Don't know what
the thinking is about this vs. systemtap these days.  There was a nice
three part series
describing ftrace/trace-cmd on lwn
( a while ago.

In terms of useability "trace-cmd" looked good to me and much more
powerful than the
current dmesg based printk style debugging.

Since the most active file systems (except for cifs.ko) on Linux
btrfs, xfs, nfs and ext4 (and
even dax and ocfs2 and nfsd and fscache etc. and of course various
drivers) already use it, seems like
it is widely accepted still and overhead is small when not logging (default).



  reply	other threads:[~2018-05-18 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  2:36 [PATCHv2][SMB3] Add kernel trace support Steve French
2018-05-18  3:28 ` Ronnie Sahlberg
2018-05-18  6:19   ` Steve French
2018-05-18  8:00     ` ronnie sahlberg
2018-05-18 18:14       ` Steve French
2018-05-18 18:46 ` Ralph Böhme
2018-05-18 20:43   ` Steve French [this message]
2018-05-19 23:22     ` Dave Chinner
2018-05-20  1:56       ` Steve French
2018-05-20 23:17         ` Dave Chinner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).