Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: "Oscar Salvador (SUSE)" <osalvador@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 David Hildenbrand <david@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	 Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	 Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
	 Pedro Falcato <pfalcato@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 2/3] mm/vma: remove mmap_action->success_hook
Date: Thu, 11 Jun 2026 10:44:33 +0100	[thread overview]
Message-ID: <aiqDUBVRGay_6P3n@lucifer> (raw)
In-Reply-To: <aiprMy4_XyNt2CYO@localhost.localdomain>

On Thu, Jun 11, 2026 at 10:00:51AM +0200, Oscar Salvador (SUSE) wrote:
> On Tue, Jun 02, 2026 at 12:06:26PM +0100, Lorenzo Stoakes wrote:
> > This hook was introduced to work around code that seemed to absolutely
> > require access to a VMA pointer upon mmap().
> >
> > However, providing this hook leaves a backdoor to drivers getting access
> > to the very thing mmap_prepare eliminates - a pointer to the VMA.
> >
> > Let's solve this contradiction by removing it.  The key intended user was
> > hugetlb, however it seems that the best course now is to avoid allowing
> > all drivers the ability to work around mmap_prepare, and find a different
> > solution there.
> >
> > Signed-off-by: Lorenzo Stoakes <ljs@kernel.org>
> > Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>
> Reach out if I can be of any help with the hugetlb thing :-)

Thanks :)

I will probably have a quick go at it at some point and just see what I can
do, hopefully I can figure something out quick, otherwise might very well
take you up on that :))

>
> Reviewed-by: Oscar Salvador <osalvador@suse.de>

Thanks!

>
>
>
> --
> Oscar Salvador
> SUSE Labs

Cheers, Lorenzo


  reply	other threads:[~2026-06-11  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 11:06 [PATCH v3 0/3] remove mmap_action success, error hooks Lorenzo Stoakes
2026-06-02 11:06 ` [PATCH v3 1/3] drivers/char/mem: eliminate unnecessary use of success_hook Lorenzo Stoakes
2026-06-03 16:25   ` Greg Kroah-Hartman
2026-06-11  7:56   ` Oscar Salvador (SUSE)
2026-06-02 11:06 ` [PATCH v3 2/3] mm/vma: remove mmap_action->success_hook Lorenzo Stoakes
2026-06-11  8:00   ` Oscar Salvador (SUSE)
2026-06-11  9:44     ` Lorenzo Stoakes [this message]
2026-06-02 11:06 ` [PATCH v3 3/3] mm/vma: eliminate mmap_action->error_hook, introduce error_override Lorenzo Stoakes
2026-06-02 12:05   ` David Hildenbrand (Arm)
2026-06-11  8:01   ` Oscar Salvador (SUSE)
2026-06-02 20:10 ` [PATCH v3 0/3] remove mmap_action success, error hooks Andrew Morton

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=aiqDUBVRGay_6P3n@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=osalvador@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox