linux-kernel - Re: [PATCH 0/3] Fixes to GCC warnings while compiling with W=1 level

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: <20200819153912.GP2026@twin.jikos.cz>
Date:   Wed, 19 Aug 2020 17:39:12 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Chris Mason <clm@...com>, David Sterba <dsterba@...e.com>,
        Josef Bacik <josef@...icpanda.com>,
        Leon Romanovsky <leonro@...dia.com>,
        linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Fixes to GCC warnings while compiling with W=1 level

On Wed, Aug 19, 2020 at 05:16:27PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
> The series of trivial fixes for GCC warnings seen while compiling with W=1.
> 
> Leon Romanovsky (3):
>   fs/btfrs: Fix -Wunused-but-set-variable warnings
>   fs/btrfs: Fix -Wignored-qualifiers warnings
>   fs/btrfs: Fix -Wmissing-prototypes warnings

The warnings from patch 2 and 3 got fixed recently, it's in the
development branch that hasn't been pushed to linux-next yet.

Patch 1 reports unused variables, we get occasional patches that just
silence the warning but it needs to be fixed properly (move setting
feature bits out of sysfs context).  As it's probably the last code
warning with W=1 left I guess I'll apply it, I don't have ETA for the
proper fix but at least this would save people time reporing it.