From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Hildenbrand <david@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Huiwen He <hehuiwen@kylinos.cn>,
Jerome Marchand <jmarchan@redhat.com>,
Qing Wang <wangqing7171@gmail.com>,
Shengming Hu <hu.shengming@zte.com.cn>,
Linux-MM <linux-mm@kvack.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [GIT PULL] tracing: Fixes for 7.0
Date: Thu, 5 Mar 2026 11:52:48 -0500 [thread overview]
Message-ID: <20260305115248.4d972cc7@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wggaToeRYv6B5L9ob=wBdVW9_gFudYxH_WJDTuhyX_Ueg@mail.gmail.com>
On Thu, 5 Mar 2026 08:44:27 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> [ Adding linux-mm and the rdma people ]
>
> On Thu, 5 Mar 2026 at 07:39, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > - Fix accounting of the memory mapped ring buffer on fork
> >
> > Memory mapping the ftrace ring buffer sets the vm_flags to DONTCOPY. But
> > this does not prevent the application from calling madvise(MADVISE_DOFORK).
>
> I wonder how many other things have this assumption.
>
> Now, many (most?) of the VM_DONTCOPY users set VM_IO too, because the
> most common reason they don't want to be copied is that it's a special
> mapping.
>
> And then madvise() does nothing.
>
> But I also get the feeling that the whole *reason* for MADV_DOFORK
> existing in the first place simply doesn't exist any more.
>
> It was added two decades ago when as a hack for the rdma people who
> wanted to mix fork (with COW) and concurrent DMA, which just didn't
> work reliably because the COW would break either way.
>
> See commit f822566165dd ("[PATCH] madvise MADV_DONTFORK/MADV_DOFORK").
>
> And that should just not be an issue any more thanks to how it's now
> done with page pinning rather than with the old GUP interfaces.
>
> So while I've pulled the tracing fix, I get the feeling that people
> should at least think about just making MADV_{DO,DONT}FORK go away.
>
> Now, Debian code search does show some users (libfabric, libibverbs),
> and maybe they actually want the forking behavior for other reasons
> too.
>
> But I get the feeling that maybe we should at least limit MADV_DOFORK
> only to the case where the *source* of the DONTFORK was the user, not
> some kernel mapping.
Right, I was a bit confused when I saw this too. I asked the memory folks
about adding the VM_IO, and Lorenzo suggested against it. You can read the
discussion here:
https://lore.kernel.org/all/e4deff21-2fb5-4f37-a7d3-ede5f69a4489@lucifer.local/
-- Steve
next prev parent reply other threads:[~2026-03-05 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260305103941.11f1b27d@gandalf.local.home>
2026-03-05 16:44 ` Linus Torvalds
2026-03-05 16:52 ` Steven Rostedt [this message]
2026-03-05 17:00 ` David Hildenbrand (Arm)
2026-03-05 17:17 ` Linus Torvalds
2026-03-05 18:59 ` David Hildenbrand (Arm)
2026-03-05 19:07 ` Jason Gunthorpe
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=20260305115248.4d972cc7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=david@kernel.org \
--cc=hehuiwen@kylinos.cn \
--cc=hu.shengming@zte.com.cn \
--cc=jgg@ziepe.ca \
--cc=jmarchan@redhat.com \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wangqing7171@gmail.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