mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: [SECURITY] mm: mremap/remap_file_pages skip fsnotify pre-content hook
       [not found] <4f296d67.bbe3e.1a1c54655f8.Coremail.18670333770@163.com>
@ 2026-11-10 12:10 ` Lorenzo Stoakes (ARM)
  2026-11-10 13:18 ` Jan Kara
  1 sibling, 0 replies; 2+ messages in thread
From: Lorenzo Stoakes (ARM) @ 2026-11-10 12:10 UTC (permalink / raw)
  To: n3rd
  Cc: linux-mm, linux-kernel, akpm, Liam R. Howlett, Jan Kara,
	Amir Goldstein, security

Stop spamming the mailing list with your unfiltered AI slop.

You've sent reports for stuff already fixed. You're reporting non-security
reports as security reports.

You're not even bothering to format your emails properly.

And what you're sending is an unreadable mess.

We have no interest in this, please just stop. Thanks.

--
Cheers, Lorenzo

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [SECURITY] mm: mremap/remap_file_pages skip fsnotify pre-content hook
       [not found] <4f296d67.bbe3e.1a1c54655f8.Coremail.18670333770@163.com>
  2026-11-10 12:10 ` [SECURITY] mm: mremap/remap_file_pages skip fsnotify pre-content hook Lorenzo Stoakes (ARM)
@ 2026-11-10 13:18 ` Jan Kara
  1 sibling, 0 replies; 2+ messages in thread
From: Jan Kara @ 2026-11-10 13:18 UTC (permalink / raw)
  To: n3rd
  Cc: linux-mm, linux-kernel, akpm, ljs, Liam R. Howlett, Jan Kara,
	Amir Goldstein, security, linux-fsdevel

Hello!

On Tue 10-11-26 19:44:43, n3rd wrote:
> 2. Problem description
> The pre-content (HSM) event contract, as stated when the feature was
> introduced, is that for every accessed file range an event covering at
> least this range is generated at least once before the file data is
> accessed. The only hook that emits that event before a mapping is
> established is fsnotify_mmap_perm() in include/linux/fsnotify.h, and its
> only caller in the whole tree is vm_mmap_pgoff() in mm/util.c, i.e. the
> mmap(2) syscall entry. The page-fault level pre-content hook was reverted
> upstream, so the syscall entry hook is the only remaining gate.
> 
> Two paths turn new file ranges into accessible mappings without ever
> reaching that gate. First, the mremap(2) EXPAND path: in-place growth
> goes through expand_vma() and expand_vma_in_place() in mm/mremap.c, and
> move growth through move_vma() and copy_vma() in mm/vma.c; neither
> mm/mremap.c nor mm/vma.c contains any fsnotify_mmap_perm() or
> security_mmap_file() call. Second, the remap_file_pages(2) emulation in
> mm/mmap.c calls security_mmap_file() and then do_mmap(MAP_POPULATE)
> directly, without fsnotify_mmap_perm().

So this is about the useful content of the email. Five pages of text is
really too much noise for this amount of useful information.

Also what you report is indeed a bug but not really a serious security
issue => let's deal with that in a public list.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-11-10 13:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <4f296d67.bbe3e.1a1c54655f8.Coremail.18670333770@163.com>
2026-11-10 12:10 ` [SECURITY] mm: mremap/remap_file_pages skip fsnotify pre-content hook Lorenzo Stoakes (ARM)
2026-11-10 13:18 ` Jan Kara

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®