linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Deepanshu Kartikey <kartikey406@gmail.com>,
	baolin.wang@linux.alibaba.com,  david@redhat.com,
	muchun.song@linux.dev, osalvador@suse.de,  kraxel@redhat.com,
	airlied@redhat.com, jgg@ziepe.ca, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org, vivek.kasireddy@intel.com,
	 syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com,
	 stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/memfd: fix information leak in hugetlb folios
Date: Sat, 22 Nov 2025 21:19:48 -0800 (PST)	[thread overview]
Message-ID: <250c36cf-6334-4b82-dbd1-5618a24271da@google.com> (raw)
In-Reply-To: <a4319c8a-4e81-00de-f184-844348d85681@google.com>

On Sat, 22 Nov 2025, Hugh Dickins wrote:
> 
> Acked-by: Hugh Dickins <hughd@google.com>
> 
> Sorry if you were all waiting on a Ack from me.  We're agreed that
> the comment above __folio_mark_uptodate() could be deleted, and that
> it would be much better if this code can be moved to a shared home
> in hugetlb later on; but for now it's more urgent to get this patch
> into hotfixes and on to Linus - please Andrew.

Ah, it is already there in mm-hotfixes-unstable, thanks;
sorry, I somehow just never saw the usual mm-commits mail.

Hugh


      reply	other threads:[~2025-11-23  5:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 14:50 Deepanshu Kartikey
2025-11-13  9:20 ` David Hildenbrand (Red Hat)
2025-11-13 12:04 ` Oscar Salvador
2025-11-23  5:03 ` Hugh Dickins
2025-11-23  5:19   ` Hugh Dickins [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=250c36cf-6334-4b82-dbd1-5618a24271da@google.com \
    --to=hughd@google.com \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=kartikey406@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com \
    --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