linux-kernel - Re: [PATCH] blackhole

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]

Date: Thu, 1 Feb 2024 11:40:59 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Breno Leitao <leitao@...ian.org>
Cc: davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com, Andrew
 Morton <akpm@...ux-foundation.org>, Mahesh Bandewar <maheshb@...gle.com>,
 weiwan@...gle.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 horms@...nel.org, andrew@...n.ch, leit@...com
Subject: Re: [PATCH] blackhole_dev: Fix buil warning

On Thu, 1 Feb 2024 10:46:08 -0800 Breno Leitao wrote:
> > Since Jiri suggested a title fix I reckon we should be a bit more
> > specific, still. Imagine this title ending up in a quote or a Fixes
> > tag, could be many things.. How about:
> > 
> >   net: blackhole_dev: fix build warning for ethh set but not used  
> 
> Sure, let me resend it.
> 
> I suppose I should recent to `net` given it is a building warning,
> right?

Not necessarily, net-next is good enough for W=1 warnings in general.
Compiler warnings only show up if the file in question or some header
it includes was modified. The linker warnings are a bit special.
If you touch any file in any module you'll see all linker warnings.