[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1520232322.k5aakv6abc.naveen@linux.ibm.com>
Date: Mon, 05 Mar 2018 12:32:57 +0530
From: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
To: Sasha Levin <Alexander.Levin@...rosoft.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>,
Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Michael Ellerman <mpe@...erman.id.au>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH AUTOSEL for 4.9 005/219] kretprobes: Ensure probe location
is at function entry
Hi Sasha,
Sasha Levin wrote:
> From: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
>
> [ Upstream commit 90ec5e89e393c76e19afc845d8f88a5dc8315919 ]
>
Sorry if this is obvious, but why was this patch picked up for -stable?
I don't see the upstream commit tagging -stable, so curious why this was
done.
I don't think this patch should be pushed to -stable since this is not
really a bug fix. There are also other dependencies for this change (see
commit a64e3f35a45f4a, for instance), including how userspace (perf)
builds out the retprobe argument. As such, please drop this from -stable
(for 3.18. 4.4 and 4.9).
Thanks,
Naveen
Powered by blists - more mailing lists