From: Steven Rostedt <rostedt@goodmis.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
"Naveen N . Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] kprobes: Allow kprobes coexist with livepatch
Date: Fri, 26 Jul 2019 14:06:34 -0400 [thread overview]
Message-ID: <20190726140634.7d0ca4dd@gandalf.local.home> (raw)
In-Reply-To: <ddda9253-27df-755b-ed51-8abc2859f076@redhat.com>
On Fri, 26 Jul 2019 13:38:41 -0400
Joe Lawrence <joe.lawrence@redhat.com> wrote:
> On 7/26/19 12:14 PM, Steven Rostedt wrote:
> > On Thu, 25 Jul 2019 22:07:52 -0400
> > Joe Lawrence <joe.lawrence@redhat.com> wrote:
> >
> >> These results reflect my underestanding of FTRACE_OPS_FL_IPMODIFY in
> >> light of your changes, so feel free to add my:
> >>
> >> Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
> >
> > Is this an urgent patch (needs to go in now and not wait for the next
> > merge window) and if so, should it be marked for stable?
> >
>
> Hi Steve,
>
> IMHO, it's not urgent.. so unless Josh or other livepatch folks say
> otherwise, I'm ok with waiting for next merge window. Given summer
> holiday schedules, that would give them more time to comment if they like.
I added it to my next merge window queue. If someone thinks it's more
urgent, I can move it to my urgent queue. I wont post to linux-next for
a few weeks, so there's time to extract it if need be.
Thanks!
-- Steve
next prev parent reply other threads:[~2019-07-26 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 6:24 [PATCH] kprobes: Allow kprobes coexist with livepatch Masami Hiramatsu
2019-07-25 13:33 ` Steven Rostedt
2019-07-26 2:07 ` Joe Lawrence
2019-07-26 16:14 ` Steven Rostedt
2019-07-26 17:38 ` Joe Lawrence
2019-07-26 18:06 ` Steven Rostedt [this message]
2019-07-27 9:41 ` Masami Hiramatsu
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=20190726140634.7d0ca4dd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.n.rao@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).