[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250321133401.GB4776@redhat.com>
Date: Fri, 21 Mar 2025 14:34:01 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org,
linux-trace-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Russell King <linux@...linux.org.uk>,
Masami Hiramatsu <mhiramat@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>,
Tong Tiangen <tongtiangen@...wei.com>
Subject: Re: [PATCH v3 0/3] kernel/events/uprobes: uprobe_write_opcode()
rewrite
On 03/21, David Hildenbrand wrote:
>
> Based on mm/unstable.
which has another fix from David in __replace_page() plus the fix from
Tong in uprobe_write_opcode().
So, Andrew, could you take this series as well? Peter, will you agree?
> Currently, uprobe_write_opcode() implements COW-breaking manually, which is
> really far from ideal.
It was never ideal, but today it is simply horrible ;)
Thanks again for your work.
Oleg.
Powered by blists - more mailing lists