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
| ||
|
Message-ID: <CAKEwX=NHdr9=hUBiZhnLZyRPsp=JwN3Vkwud2XEn3=pNurYGpQ@mail.gmail.com> Date: Tue, 26 Dec 2023 16:23:53 -0800 From: Nhat Pham <nphamcs@...il.com> To: Chris Li <chrisl@...nel.org> Cc: syzbot <syzbot+3eff5e51bf1db122a16e@...kaller.appspotmail.com>, akpm@...ux-foundation.org, davem@...emloft.net, herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com, yosryahmed@...gle.com, zhouchengming@...edance.com Subject: Re: [syzbot] [crypto?] general protection fault in scatterwalk_copychunks (5) On Tue, Dec 26, 2023 at 3:30 PM Chris Li <chrisl@...nel.org> wrote: > > Again, sorry I was looking at the decompression side rather than the > compression side. The compression side does not even offer a safe > version of the compression function. > That seems to be dangerous. It seems for now we should make the zswap > roll back to 2 page buffer until we have a safe way to do compression > without overwriting the output buffers. Unfortunately, I think this is the way - at least until we rework the crypto/compression API (if that's even possible?). I still think the 2 page buffer is dumb, but it is what it is :(
Powered by blists - more mailing lists