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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 15 Oct 2020 12:01:27 -0600
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Vitor Massaru Iha <vitor@...saru.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Brendan Higgins <brendanhiggins@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: linux-next: build warnings after merge of the kunit-next tree

On 10/15/20 4:43 AM, Vitor Massaru Iha wrote:
> Hi Stephen,
> 
> On Thu, Oct 15, 2020 at 2:31 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> Hi all,
>>
>> After merging the kunit-next tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> lib/bitfield_kunit.c: In function 'test_bitfields_compile':
>> lib/bitfield_kunit.c:136:21: warning: unsigned conversion from 'int' to 'u16' {aka 'short unsigned int'} changes value from '393216' to '0' [-Woverflow]
>>    136 |  u16_encode_bits(0, 0x60000);
>>        |                     ^~~~~~~
>> At top level:
>> lib/bitfield_kunit.c:129:20: warning: 'test_bitfields_compile' defined but not used [-Wunused-function]
>>    129 | static void __init test_bitfields_compile(struct kunit *context)
>>        |                    ^~~~~~~~~~~~~~~~~~~~~~
>>
>> Introduced by commit
>>
>>    d2585f5164c2 ("lib: kunit: add bitfield test conversion to KUnit")
> 
> I saw the problem, I will send the patch.
> 

Please send the fix in as soon as possible. I will go ahead and send the
pull request and will apply the fix in rc2.

thanks,
-- Shuah

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ