linux-kernel - Re: linux-next: build warnings after merge of the file-locks 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <934008823b152cbe9bf170c866d2c0aa8552e61e.camel@kernel.org>
Date:   Mon, 23 Aug 2021 06:14:23 -0400
From:   Jeff Layton <jlayton@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the file-locks tree

On Mon, 2021-08-23 at 10:19 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the file-locks tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
> 
> fs/remap_range.c: In function 'remap_verify_area':
> fs/remap_range.c:102:16: warning: unused variable 'inode' [-Wunused-variable]
>   102 |  struct inode *inode = file_inode(file);
>       |                ^~~~~
> 
> Also from the arm multi_v7_defconfig build:
> 
> fs/locks.c: In function 'fcntl_setlk64':
> fs/locks.c:2509:16: warning: unused variable 'inode' [-Wunused-variable]
>  2509 |  struct inode *inode = locks_inode(filp);
>       |                ^~~~~
> 
> And from the x86_64 allmodconfig build:
> 
> fs/9p/vfs_file.c: In function 'v9fs_file_lock_dotl':
> fs/9p/vfs_file.c:322:1: warning: label 'out_err' defined but not used [-Wunused-label]
>   322 | out_err:
>       | ^~~~~~~
> 
> Introduced by commit
> 
>   3efee0567b4a ("fs: remove mandatory file locking support")
> 

Thanks Stephen. I'll fix those up.

Cheers,
-- 
Jeff Layton <jlayton@...nel.org>