mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, mhiramat@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: kprobes sanity test fails on next-20190708
Date: Mon, 8 Jul 2019 16:56:50 +0100	[thread overview]
Message-ID: <a19faa89-d318-fe21-9952-b0f842240ba5@arm.com> (raw)
In-Reply-To: <20190708141136.GA3239@localhost.localdomain>

Hi,

On 08/07/2019 15:11, Anders Roxell wrote:
> argh... resending, with plaintext... Sorry =/
> 
> I tried to build a next-201908 defconfig + CONFIG_KPROBES=y and
> CONFIG_KPROBES_SANITY_TEST=y
> 
> I get the following Call trace, any ideas?
> I've tried tags back to next-20190525 and they also failes... I haven't
> found a commit that works yet.
> 
> [    0.098694] Kprobe smoke test: started
> [    0.102001] audit: type=2000 audit(0.088:1): state=initialized
> audit_enabled=0 res=1
> [    0.104753] Internal error: aarch64 BRK: f2000004 [#1] PREEMPT SMP

This sounds like the issue Mark reported:
https://lore.kernel.org/r/20190702165008.GC34718@lakrids.cambridge.arm.com

It doesn't look like Steve's patch has percolated into next yet:
https://lore.kernel.org/lkml/20190703103715.32579c25@gandalf.local.home/

Could you give that a try to see if this is a new issue?


Thanks,

James

  reply	other threads:[~2019-07-08 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 14:11 Anders Roxell
2019-07-08 15:56 ` James Morse [this message]
2019-07-09 10:19   ` Anders Roxell
2019-07-09 12:36     ` Masami Hiramatsu
2019-07-09 15:25       ` Steven Rostedt
2019-07-09 15:37         ` Mark Rutland
2019-07-09 15:40           ` Steven Rostedt
2019-07-10  2:46             ` 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=a19faa89-d318-fe21-9952-b0f842240ba5@arm.com \
    --to=james.morse@arm.com \
    --cc=anders.roxell@linaro.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@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
all inboxes | Powered by JetHome®