linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: Dynamic ftrace self test broken on ARM
Date: Wed, 20 Jun 2018 21:06:38 +0200	[thread overview]
Message-ID: <7904ed3fe9f59a54526d64f366915b43@agner.ch> (raw)
In-Reply-To: <20180620101311.0bcd73d3@gandalf.local.home>

On 20.06.2018 16:13, Steven Rostedt wrote:
> On Wed, 20 Jun 2018 15:51:55 +0200
> Stefan Agner <stefan@agner.ch> wrote:
> 
> 
>> v4.9 seems to work, so I started bisecting. It turned out that commit
>> 6f05d0761af6 ("ARM: 8668/1: ftrace: Fix dynamic ftrace with DEBUG_RODATA
>> and !FRAME_POINTER") broke it, introduced during the v4.12 merge window.
> 
> That patch doesn't appear to be the cause. It could have been a failed
> bisect. Does the commit before that commit work? Does that commit fail?

Pretty sure it is that one. Reverting it on top of v4.18-rc1 fixes it...

> 
> It may be due to some other RODATA change though. That is actually one
> of my thoughts when looking at the bug.

CONFIG_STRICT_KERNEL_RWX=y is set, will test without.

--
Stefan

  reply	other threads:[~2018-06-20 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 21:09 Dynamic ftrace self test broken on ARM Stefan Agner
2018-06-18 21:54 ` Steven Rostedt
2018-06-19  8:16   ` Stefan Agner
2018-06-19 13:17     ` Steven Rostedt
2018-06-20 13:51       ` Stefan Agner
2018-06-20 14:13         ` Steven Rostedt
2018-06-20 19:06           ` Stefan Agner [this message]
2018-06-20 21:32             ` Stefan Agner
2018-06-20 22:45               ` Stefan Agner
2018-06-20 23:07                 ` Russell King - ARM Linux
2018-06-21  1:29                   ` Steven Rostedt
2018-06-21  7:25                     ` Stefan Agner
2018-06-21 13:51                       ` Steven Rostedt

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=7904ed3fe9f59a54526d64f366915b43@agner.ch \
    --to=stefan@agner.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).