mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donald Hoskins <grommish@gmail.com>
To: yaliang.wang@windriver.com
Cc: akpm@linux-foundation.org, anshuman.khandual@arm.com,
	geert@linux-m68k.org, huangpei@loongson.cn, kumba@gentoo.org,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	penberg@kernel.org, rppt@kernel.org, tsbogend@alpha.franken.de
Subject: Re: [PATCH] MIPS: pgalloc: fix memory leak caused by pgd_free()
Date: Sun, 3 Apr 2022 00:15:04 -0400	[thread overview]
Message-ID: <bb6473ac-3a12-9667-9425-7b61746e8078@gmail.com> (raw)
In-Reply-To: <20220310113116.2068859-1-yaliang.wang@windriver.com>

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.


      parent reply	other threads:[~2022-04-03  4:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 11:31 yaliang.wang
2022-03-14 14:51 ` Thomas Bogendoerfer
2022-04-02 13:48 ` Maciej W. Rozycki
2022-04-03  3:34   ` Andrew Holmes
2022-04-03 10:37     ` Maciej W. Rozycki
2022-04-04 13:16       ` Andrew Powers-Holmes
2022-04-05  9:42         ` Maciej W. Rozycki
2022-04-05 10:45           ` Thomas Bogendoerfer
2022-04-05 11:31             ` Maciej W. Rozycki
2022-04-04 21:10       ` Joshua Kinard
2022-04-03  4:15 ` Donald Hoskins [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb6473ac-3a12-9667-9425-7b61746e8078@gmail.com \
    --to=grommish@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=geert@linux-m68k.org \
    --cc=huangpei@loongson.cn \
    --cc=kumba@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=rppt@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=yaliang.wang@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®