linux-kernel - Re: linux-next: build warning after merge of the pidfd-fixes 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:   Mon, 9 Mar 2020 23:37:32 +0100
From:   Christian Brauner <christian.brauner@...ntu.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Christian Brauner <christian@...uner.io>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the pidfd-fixes tree

On Tue, Mar 10, 2020 at 08:07:58AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the pidfd-fixes tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> In file included from include/linux/rwsem.h:18,
>                  from include/linux/mm_types.h:11,
>                  from include/linux/mmzone.h:21,
>                  from include/linux/gfp.h:6,
>                  from include/linux/mm.h:10,
>                  from kernel/pid.c:30:
> kernel/pid.c: In function 'alloc_pid':
> include/linux/err.h:26:9: warning: 'retval' may be used uninitialized in this function [-Wmaybe-uninitialized]
>    26 |  return (void *) error;
>       |         ^~~~~~~~~~~~~~
> kernel/pid.c:168:6: note: 'retval' was declared here
>   168 |  int retval;
>       |      ^~~~~~
> 
> Introduced by commit
> 
>   8deb24dcb89c ("pid: make ENOMEM return value more obvious")

Thanks, will fix now. Sorry for the noise!
Christian;