public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: kernel test robot <lkp@intel.com>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2] scsi: sd_zbc: trace zone append emulation
Date: Sat, 26 Nov 2022 11:35:38 +0900	[thread overview]
Message-ID: <969cf476-d732-9566-63e4-01fb23fa74fe@opensource.wdc.com> (raw)
In-Reply-To: <yq1h6ymo3wp.fsf@ca-mkp.ca.oracle.com>

On 11/26/22 11:18, Martin K. Petersen wrote:
> 
> Johannes,
> 
>>>>> ERROR: modpost: "__tracepoint_scsi_prepare_zone_append" [drivers/scsi/sd_mod.ko] undefined!
>>>>> ERROR: modpost: "__SCK__tp_func_scsi_prepare_zone_append" [drivers/scsi/sd_mod.ko] undefined!
>>>>> ERROR: modpost: "__SCK__tp_func_scsi_zone_wp_update" [drivers/scsi/sd_mod.ko] undefined!
>>>>> ERROR: modpost: "__SCT__tp_func_scsi_zone_wp_update" [drivers/scsi/sd_mod.ko] undefined!
>>>>> ERROR: modpost: "__tracepoint_scsi_zone_wp_update" [drivers/scsi/sd_mod.ko] undefined!
>>>>> ERROR: modpost: "__SCT__tp_func_scsi_prepare_zone_append" [drivers/scsi/sd_mod.ko] undefined!
>>>
>>
>> I have no clue what modpost is trying to tell me here. These tracepoints aren't
>> in any way different to the other tracepoints in SCSI.
> 
> Haven't investigated. But I get the same errors building scsi-staging
> with your patch applied. Builds fine without it. gcc 12.1.
> 

This is missing:

diff --git a/drivers/scsi/scsi_trace.c b/drivers/scsi/scsi_trace.c
index 41a950075913..224b38c0fb0f 100644
--- a/drivers/scsi/scsi_trace.c
+++ b/drivers/scsi/scsi_trace.c
@@ -389,3 +389,4 @@ scsi_trace_parse_cdb(struct trace_seq *p, unsigned
char *cdb, int len)
                return scsi_trace_misc(p, cdb, len);
        }
 }
+EXPORT_SYMBOL(scsi_trace_parse_cdb);
diff --git a/drivers/scsi/sd_zbc.c b/drivers/scsi/sd_zbc.c
index 956d1982c51b..e7a0e1ace6d0 100644
--- a/drivers/scsi/sd_zbc.c
+++ b/drivers/scsi/sd_zbc.c
@@ -18,6 +18,7 @@
 #include <scsi/scsi.h>
 #include <scsi/scsi_cmnd.h>

+#define CREATE_TRACE_POINTS
 #include <trace/events/scsi.h>

 #include "sd.h"

With that, it compiles fine.

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2022-11-26  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 12:01 [PATCH v2] scsi: sd_zbc: trace zone append emulation Johannes Thumshirn
2022-11-14 22:42 ` kernel test robot
2022-11-15  2:24 ` kernel test robot
2022-11-15  5:26 ` kernel test robot
2022-11-18  8:31   ` Johannes Thumshirn
2022-11-26  2:18     ` Martin K. Petersen
2022-11-26  2:35       ` Damien Le Moal [this message]
2022-11-28  8:54         ` Johannes Thumshirn
2022-11-28  9:02           ` Johannes Thumshirn

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=969cf476-d732-9566-63e4-01fb23fa74fe@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox