All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: <target-devel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<linux@yadro.com>
Subject: Re: [PATCH] scsi: target: core: Add CONTROL field for trace events
Date: Fri, 02 Oct 2020 18:41:06 -0400	[thread overview]
Message-ID: <yq11rigfdza.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200929125957.83069-1-r.bolshakov@yadro.com> (Roman Bolshakov's message of "Tue, 29 Sep 2020 15:59:57 +0300")


Roman,

> trace-cmd report doesn't show events from target subsystem because
> scsi_command_size() leaks through event format string:

Applied to 5.10/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux@yadro.com
Subject: Re: [PATCH] scsi: target: core: Add CONTROL field for trace events
Date: Fri, 02 Oct 2020 22:41:06 +0000	[thread overview]
Message-ID: <yq11rigfdza.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200929125957.83069-1-r.bolshakov@yadro.com> (Roman Bolshakov's message of "Tue, 29 Sep 2020 15:59:57 +0300")


Roman,

> trace-cmd report doesn't show events from target subsystem because
> scsi_command_size() leaks through event format string:

Applied to 5.10/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2020-10-02 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 12:59 [PATCH] scsi: target: core: Add CONTROL field for trace events Roman Bolshakov
2020-09-29 12:59 ` Roman Bolshakov
2020-10-02 17:58 ` Mike Christie
2020-10-02 17:58   ` Mike Christie
2020-10-02 22:41 ` Martin K. Petersen [this message]
2020-10-02 22:41   ` Martin K. Petersen
2020-10-07  3:48 ` Martin K. Petersen
2020-10-07  3:48   ` Martin K. Petersen

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=yq11rigfdza.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@yadro.com \
    --cc=r.bolshakov@yadro.com \
    --cc=target-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.