From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Tony Luck <tony.luck@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
sparse@chrisli.org, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@kernel.org>,
linux-tip-commits@vger.kernel.org, akataria@vmware.com,
anil.s.keshavamurthy@intel.com,
"Suzuki K. Poulose" <suzuki@in.ibm.com>,
Fenghua Yu <fenghua.yu@intel.com>, Arnd Bergmann <arnd@arndb.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>,
yrl.pp-manager.tt@hitachi.com,
Thomas Gleixner <tglx@linutronix.de>,
Kevin Hao <haokexin@gmail.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
linuxppc-dev@lists.ozlabs.org, rdunlap@infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl9pf@gmx.de, Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Re: [PATCH v5 2/2] [BUGFIX] kprobes: Fix "Failed to find blacklist" error on ia64 and ppc64
Date: Tue, 15 Jul 2014 02:24:49 +0000 [thread overview]
Message-ID: <53C490F1.4020402@hitachi.com> (raw)
In-Reply-To: <1405390262.17767.5.camel@concordia>
(2014/07/15 11:11), Michael Ellerman wrote:
> On Mon, 2014-07-14 at 10:17 -0700, Tony Luck wrote:
>> On Tue, Jul 8, 2014 at 5:07 AM, Masami Hiramatsu
>> <masami.hiramatsu.pt@hitachi.com> wrote:
>>> Ping?
>>>
>>> This patch can be applied without 1/2, and will fix ia64/ppc64 problem.
>>
>> Is somebody going to push this upstream? Another week has gone by,
>> we are at -rc5, and I'm still seeing the
>>
>> Failed to find blacklist a00000010133b150
>>
>> messages on ia64.
>
> I don't see those messages on ppc64, I don't know where the original report
> that it was broken on ppc64 came from. So I'm a bit lukewarm on the patch.
Right, on ppc64(ABIv1) it may be silently failed. Because each function
descriptor has another entry on kallsyms, original code can't detect
that. On the other hand, ia64's function descriptors have no entries,
so it can detect the failure on boot.
This patch adds new detection code using kernel_text_address() and
translates function descriptor to function entry.
Thank you,
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-07-15 2:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 2:23 [PATCH v4] [BUGFIX] kprobes: Fix "Failed to find blacklist" error on ia64 and ppc64 Masami Hiramatsu
2014-06-30 3:14 ` Masami Hiramatsu
2014-06-30 11:36 ` Michael Ellerman
2014-07-01 2:21 ` Masami Hiramatsu
2014-07-02 4:41 ` Michael Ellerman
2014-07-02 6:39 ` Masami Hiramatsu
2014-07-02 6:56 ` Michael Ellerman
2014-07-02 7:16 ` Masami Hiramatsu
2014-07-02 7:00 ` [PATCH v5 2/2] " Masami Hiramatsu
2014-07-08 12:07 ` Masami Hiramatsu
2014-07-14 17:17 ` Tony Luck
2014-07-15 2:11 ` Michael Ellerman
2014-07-15 2:24 ` Masami Hiramatsu [this message]
2014-07-15 3:16 ` Michael Ellerman
2014-07-15 3:19 ` Michael Ellerman
2014-07-15 7:16 ` Benjamin Herrenschmidt
2014-07-15 10:09 ` Masami Hiramatsu
2014-07-16 13:28 ` Ingo Molnar
2014-07-17 7:10 ` Masami Hiramatsu
2014-07-17 9:40 ` Ingo Molnar
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=53C490F1.4020402@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=dl9pf@gmx.de \
--cc=fenghua.yu@intel.com \
--cc=haokexin@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sparse@chrisli.org \
--cc=suzuki@in.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=yrl.pp-manager.tt@hitachi.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