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]
Date:   Sun, 3 Apr 2022 00:15:04 -0400
From:   Donald Hoskins <grommish@...il.com>
To:     yaliang.wang@...driver.com
Cc:     akpm@...ux-foundation.org, anshuman.khandual@....com,
        geert@...ux-m68k.org, huangpei@...ngson.cn, kumba@...too.org,
        linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
        penberg@...nel.org, rppt@...nel.org, tsbogend@...ha.franken.de
Subject: Re: [PATCH] MIPS: pgalloc: fix memory leak caused by pgd_free()

Hi there,

This fix should backported.  Effectively, all mips64-based Cavium Octeon 
processors have been broken since the original commit; this has been a 
persistent and surreptitious issue for the OpenWrt community since 
nearly a year ago (referencing 
https://forum.openwrt.org/t/upstream-kernel-memleak-5-10-octeon-ethernet-ko/111827/), 
and nearly ended with OpenWrt marking the target as entirely unsupported 
and moving on.

We understand that there are ultimately few users of mips64, but it's 
really important that our memory management work. While OpenWrt can 
backport until upstream inclusion, I am sure there are other users and 
software platforms unaware of this fix (and unable to take advantage of 
it), thus making those platforms on this arch completely unusable.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ