mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hongfu Li <hongfu.li@linux.dev>
Cc: hughd@google.com, baolin.wang@linux.alibaba.com,
	vivek.kasireddy@intel.com, muchun.song@linux.dev,
	osalvador@suse.de, david@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Hongfu Li <lihongfu@kylinos.cn>
Subject: Re: [PATCH v2] mm/memfd: fix hugetlb reservation accounting in error paths
Date: Tue, 8 Sep 2026 19:54:18 -0700	[thread overview]
Message-ID: <20260908195418.c5ef0f3fbc2b3bec405cd652@linux-foundation.org> (raw)
In-Reply-To: <638ae9ae-2cbc-47a4-85fd-52b67b74e351@linux.dev>

On Tue, 8 Sep 2026 09:35:23 +0800 Hongfu Li <hongfu.li@linux.dev> wrote:

> > To help people understand why we propose a backport and to help others
> > understand the impact the fix will have upon their system, I'll paste
> > the above into the changelog.  Please send any necessary corrections.
> >
> >
> > Please also update your prompts (if using them) to ensure that the
> > changelogging includes this info in the future.
> >
> >
> > I'll queue it for testing and shall await maintainer review.
> 
> 
> Thanks for the detailed explanation.
> 
> I've updated the changelog to include the userspace-visible effects
> and long-term impact as suggested.
> 
> Would you prefer that I send a v2 now, or should I wait for maintainer
> feedback first?

Well, it's been five days.  There have been 200,000 patches since then,
so this series is at the far right end of the asymptote.  Resend when
convenient, please.


      reply	other threads:[~2026-09-09  2:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  3:01 Hongfu Li
2026-09-03 20:21 ` Andrew Morton
2026-09-08  1:35   ` Hongfu Li
2026-09-09  2:54     ` Andrew Morton [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=20260908195418.c5ef0f3fbc2b3bec405cd652@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=hongfu.li@linux.dev \
    --cc=hughd@google.com \
    --cc=lihongfu@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=vivek.kasireddy@intel.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®