netdev - Re: [PATCH v2 net-next] netlink: specs: add conntrack dump and stats dump support

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]

Message-ID: <20250212105841.03ccd91c@kernel.org>
Date: Wed, 12 Feb 2025 10:58:41 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Simon Horman <horms@...nel.org>
Cc: Florian Westphal <fw@...len.de>, netdev@...r.kernel.org,
 netfilter-devel@...r.kernel.org, donald.hunter@...il.com
Subject: Re: [PATCH v2 net-next] netlink: specs: add conntrack dump and
 stats dump support

On Wed, 12 Feb 2025 18:20:07 +0000 Simon Horman wrote:
> > > Looks like the tree has both v1 and v2 appliedto it.
> > > 
> > > v1 added 'ctnetlink.yaml', I renamed it to 'conntrack.yaml' in v2 as
> > > thats what Donald requested.  
> > 
> > I see. We need to clean the HTML output more thoroughly in the CI 🤔️
> > I brought the patch back, let's see what happens on next run.  
> 
> It seems happy now.
> 
> Should I work on a fix for NIPA?

I'm not gonna say no :)

The problem is a bit broader than just this exact instance.
In general we don't clean up build artifacts to take advantage 
of incremental builds. So when files move or get renamed the old
artifacts are left in place occasionally causing issues.

I wonder what the best fix is. Feels like wiping the tree clean
periodically (once a day or two?) could be best? Something like 
creating a local file, once that file is more than 2 days old
wipe the tree pristine clean by all means possible, and then
create the file again?