Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hao Ge <hao.ge@linux.dev>
Cc: Suren Baghdasaryan <surenb@google.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/2] alloc_tag: fix a leak and a deadlock around shutdown_mem_profiling()
Date: Wed, 26 Aug 2026 20:39:14 -0700	[thread overview]
Message-ID: <20260826203914.347c42aa00081ee9e0eb858a@linux-foundation.org> (raw)
In-Reply-To: <20260817062726.106511-1-hao.ge@linux.dev>

On Mon, 17 Aug 2026 14:27:24 +0800 Hao Ge <hao.ge@linux.dev> wrote:

> Two fixes for issues reported by sashiko:
> 
>   1. percpu counter leak on modules loaded after profiling is disabled.
>   2. AB-BA deadlock between module load and /proc/allocinfo readers.
> 

Thanks.  AI review asked two questions.  One pertinent to your
alterations and one pertinent to Suren ;)

	https://sashiko.dev/#/patchset/20260817062726.106511-1-hao.ge@linux.dev

I'll queue the patchset for 7.3-rc1, with a note-to-self.


  parent reply	other threads:[~2026-08-27  3:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  6:27 [PATCH v2 0/2] alloc_tag: fix a leak and a deadlock around shutdown_mem_profiling() Hao Ge
2026-08-17  6:27 ` [PATCH 1/2] alloc_tag: skip percpu counter allocation when profiling is disabled Hao Ge
2026-08-24 16:44   ` Suren Baghdasaryan
2026-08-17  6:27 ` [PATCH 2/2] alloc_tag: remove /proc/allocinfo outside of mod_lock Hao Ge
2026-08-24 16:46   ` Suren Baghdasaryan
2026-08-27  3:39 ` Andrew Morton [this message]
2026-08-28  3:11   ` [PATCH v2 0/2] alloc_tag: fix a leak and a deadlock around shutdown_mem_profiling() Hao Ge
  -- strict thread matches above, loose matches on Subject: below --
2026-08-17  6:27 Hao Ge
2026-08-17  6:26 Hao Ge

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=20260826203914.347c42aa00081ee9e0eb858a@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hao.ge@linux.dev \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=surenb@google.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