lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1554439969.24612.41.camel@HansenPartnership.com> Date: Thu, 04 Apr 2019 21:52:49 -0700 From: James Bottomley <James.Bottomley@...senPartnership.com> To: Bart Van Assche <bvanassche@....org>, Stephen Rothwell <sfr@...b.auug.org.au> Cc: Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "Martin K. Petersen" <martin.petersen@...cle.com> Subject: Re: linux-next: build warning after merge of the scsi tree On Thu, 2019-04-04 at 21:30 -0700, Bart Van Assche wrote: > On 4/4/19 8:25 PM, Stephen Rothwell wrote: > > Hi James, > > > > After merging the scsi tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > drivers/scsi/lpfc/lpfc_nvme.c:2140:1: warning: > > 'lpfc_nvme_lport_unreg_wait' defined but not used [-Wunused- > > function] > > lpfc_nvme_lport_unreg_wait(struct lpfc_vport *vport, > > ^~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > Introduced by commit > > > > 3999df75bccb ("scsi: lpfc: Declare local functions static") > > > > It use is guarded by IS_ENABLED(CONFIG_NVME_FC). > > I will have a closer look at this tomorrow. In the meantime, we can just revert the patch. Making functions static serves no real purpose except it does tell the compiler they have to be used internally which is where the problem is coming from. Once the issue is sorted, the static patch can be reapplied. James
Powered by blists - more mailing lists