From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: kernel test robot <lkp@intel.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@opensource.wdc.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2] scsi: sd_zbc: trace zone append emulation
Date: Fri, 25 Nov 2022 21:18:48 -0500 [thread overview]
Message-ID: <yq1h6ymo3wp.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <7c758dc6-692c-3aeb-a0de-05e4134f839f@wdc.com> (Johannes Thumshirn's message of "Fri, 18 Nov 2022 08:31:26 +0000")
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.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-11-26 2:19 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 [this message]
2022-11-26 2:35 ` Damien Le Moal
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=yq1h6ymo3wp.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=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=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