From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>, linux-mm@kvack.org
Subject: Re: Is uprobe_write_opcode() OK?
Date: Mon, 24 Feb 2025 10:53:05 +0100 [thread overview]
Message-ID: <d7971673-19ed-448a-9e54-8ffbde5059dc@redhat.com> (raw)
In-Reply-To: <Z7eQx1eLtqTnIkX7@casper.infradead.org>
On 20.02.25 21:29, Matthew Wilcox wrote:
> I just wrote the patch below, but now I'm wondering if it's
> perpetuating the mistake of not using our existing COW mechanism
> to handle uprobes. Anyone looked at this code recently?
I have a bigger rewrite in the queue:
https://lore.kernel.org/linux-mm/20240604122548.359952-2-david@redhat.com/T/
That will do exactly that: leave COW to core MM.
I'll respin that soonish.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-02-24 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 20:29 Matthew Wilcox
2025-02-24 9:53 ` David Hildenbrand [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=d7971673-19ed-448a-9e54-8ffbde5059dc@redhat.com \
--to=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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