linux-kernel - Re: linux-next: build failure after merge of the crypto 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240313021211.47293-1-21cnbao@gmail.com>
Date: Wed, 13 Mar 2024 15:12:11 +1300
From: Barry Song <21cnbao@...il.com>
To: ebiggers@...nel.org
Cc: akpm@...ux-foundation.org,
	herbert@...dor.apana.org.au,
	linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org,
	sfr@...b.auug.org.au,
	v-songbaohua@...o.com
Subject: Re: linux-next: build failure after merge of the crypto tree

> The only user of comp_alg_common was the crypto stats, and it was introduced by
> a refactoring of the crypto stats (commit 0a742389bcc0, "crypto: acomp - Count
> error stats differently"), so it seems appropriate to remove it for now.
> 
> If you could go through my patch and explain what other unused code related to
> the crypto stats you might consider to be "infrastructure" that should not be
> removed, that would be helpful.

Hi Eric,
that user is mm/zswap [1], apologize it was not in crypto tree. I guess you might
just need a new version to keep that one :-)

[1] https://lore.kernel.org/linux-mm/20240222081135.173040-2-21cnbao@gmail.com/ 

> - Eric

Thanks
Barry