All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daehyeon Ko <4ncienth@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/secretmem: prevent uncharged mremap expansion after fork
Date: Tue, 18 Aug 2026 12:42:12 +0900	[thread overview]
Message-ID: <20260818034212.1761451-1-4ncienth@gmail.com> (raw)
In-Reply-To: <20260817154356.552ccde5d279f6e0a9ef0ff2@linux-foundation.org>

Thanks for the review.

Yes, this patch was developed with AI assistance. I should have included the
required Assisted-by trailer, and I apologize for the omission.

The related issue is pertinent. Lorenzo's follow-up shows that the underlying
problem is broader than the fork/mremap path: secretmem accounting follows the
VMA lifetime, while the folios remain unevictable until inode eviction. My
VM_DONTEXPAND approach only blocks one path and is not an appropriate fix.

Please drop this patch. I will test Lorenzo's follow-up patch and report the
results on that thread.

Thanks,
Daehyeon


      reply	other threads:[~2026-08-18  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 22:53 [PATCH] mm/secretmem: prevent uncharged mremap expansion after fork Daehyeon Ko
2026-08-14  8:21 ` Lorenzo Stoakes (ARM)
2026-08-17 22:43 ` Andrew Morton
2026-08-18  3:42   ` Daehyeon Ko [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=20260818034212.1761451-1-4ncienth@gmail.com \
    --to=4ncienth@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.