linux-kernel - Re: linux-next: build warnings after merge of the scsi-mkp tree

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 29 Jun 2017 18:35:35 +0000
From:   "Madhani, Himanshu" <Himanshu.Madhani@...ium.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
CC:     James Bottomley <James.Bottomley@...senPartnership.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "Trapp, Darren" <Darren.Trapp@...ium.com>,
        "Grigsby, Duane" <Duane.Grigsby@...ium.com>,
        Anil Gurumurthy <anil.gurumurhty@...ium.com>,
        "Malavali, Giridhar" <Giridhar.Malavali@...ium.com>,
        Hannes Reinecke <hare@...e.com>
Subject: Re: linux-next: build warnings after merge of the scsi-mkp tree

Hi Stephen, James,

> On Jun 28, 2017, at 10:07 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> Hi James,
> 
> This has now migrated to the scsi tree.
> 
> On Wed, 28 Jun 2017 15:55:10 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> 
>> After merging the scsi-mkp tree, today's linux-next build
>> (powerpc_ppc64_defconfig) produced these warnings:
>> 
>> In file included from include/linux/byteorder/big_endian.h:4:0,
>>                 from arch/powerpc/include/uapi/asm/byteorder.h:13,
>>                 from include/asm-generic/bitops/le.h:5,
>>                 from arch/powerpc/include/asm/bitops.h:246,
>>                 from include/linux/bitops.h:36,
>>                 from include/linux/kernel.h:10,
>>                 from include/asm-generic/bug.h:15,
>>                 from arch/powerpc/include/asm/bug.h:127,
>>                 from include/linux/bug.h:4,
>>                 from arch/powerpc/include/asm/mmu.h:125,
>>                 from arch/powerpc/include/asm/lppaca.h:36,
>>                 from arch/powerpc/include/asm/paca.h:21,
>>                 from arch/powerpc/include/asm/current.h:16,
>>                 from include/linux/sched.h:11,
>>                 from include/linux/blkdev.h:4,
>>                 from include/linux/blk-mq.h:4,
>>                 from drivers/scsi/qla2xxx/qla_nvme.h:10,
>>                 from drivers/scsi/qla2xxx/qla_nvme.c:7:
>> drivers/scsi/qla2xxx/qla_nvme.c: In function 'qla2x00_start_nvme_mq':
>> include/uapi/linux/byteorder/big_endian.h:32:26: warning: large integer implicitly truncated to unsigned type [-Woverflow]
>> #define __cpu_to_le32(x) ((__force __le32)__swab32((x)))
>>                          ^
>> include/linux/byteorder/generic.h:87:21: note: in expansion of macro '__cpu_to_le32'
>> #define cpu_to_le32 __cpu_to_le32
>>                     ^
>> drivers/scsi/qla2xxx/qla_nvme.c:444:27: note: in expansion of macro 'cpu_to_le32'
>>    cont_pkt->entry_type = cpu_to_le32(CONTINUE_A64_TYPE);
>>                           ^
>> drivers/scsi/qla2xxx/qla_nvme.c: At top level:
>> drivers/scsi/qla2xxx/qla_nvme.c:667:13: warning: 'qla_nvme_unregister_remote_port' defined but not used [-Wunused-function]
>> static void qla_nvme_unregister_remote_port(struct work_struct *work)
>>             ^
>> drivers/scsi/qla2xxx/qla_nvme.c:604:12: warning: 'qla_nvme_wait_on_rport_del' defined but not used [-Wunused-function]
>> static int qla_nvme_wait_on_rport_del(fc_port_t *fcport)
>>            ^
>> drivers/scsi/qla2xxx/qla_nvme.c:634:13: warning: 'qla_nvme_abort_all' defined but not used [-Wunused-function]
>> static void qla_nvme_abort_all(fc_port_t *fcport)
>>             ^
>> 
>> Introduced by commit
>> 
>>  e84067d74301 ("scsi: qla2xxx: Add FC-NVMe F/W initialization and transport registration")
> 
> -- 
> Cheers,
> Stephen Rothwell


Would it be okay if we send patch to address this warnings in couple days? 

Thanks,
- Himanshu