From: Anton Blanchard <anton@samba.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: mpe@ellerman.id.au, chris@distroguy.com, npiggin@gmail.com,
linux-kernel@vger.kernel.org, paulus@samba.org,
aneesh.kumar@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH] ppc64/kprobe: Fix oops when kprobed on 'stdu' instruction
Date: Tue, 11 Apr 2017 08:37:21 +1000 [thread overview]
Message-ID: <20170411083721.0c9f9177@kryten> (raw)
In-Reply-To: <1491837657-4918-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com>
Hi Ravi,
> If we set a kprobe on a 'stdu' instruction on powerpc64, we see a
> kernel OOPS:
Ouch! We should mark this for stable.
Anton
prev parent reply other threads:[~2017-04-10 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:20 [PATCH] ppc64/kprobe: Fix oops when kprobed on 'stdu' instruction Ravi Bangoria
2017-04-10 16:19 ` Naveen N. Rao
2017-04-10 22:37 ` Anton Blanchard [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=20170411083721.0c9f9177@kryten \
--to=anton@samba.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=chris@distroguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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).