All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215621] Warning: Unable to mark rodata read only on this CPU. (PPC970MP)
Date: Sun, 20 Feb 2022 18:10:22 +0000	[thread overview]
Message-ID: <bug-215621-206035-VuFAXSHQNL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215621-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215621

Erhard F. (erhard_f@mailbox.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Erhard F. (erhard_f@mailbox.org) ---
Erm ok, so it seems I did not check this thoroughly...

If MMU_FTRS_PPC970 doesn't provide MMU_FTR_KERNEL_RO then perhaps
CONFIG_STRICT_KERNEL_RWX can be skipped in the .config so it can't be wrongly
selected?

Anyhow you are correct that this is not a bug. Thanks for the background!

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-02-20 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  1:04 [Bug 215621] New: Warning: Unable to mark rodata read only on this CPU. (PPC970MP) bugzilla-daemon
2022-02-19  1:04 ` [Bug 215621] " bugzilla-daemon
2022-02-20 16:38 ` bugzilla-daemon
2022-02-20 18:10 ` bugzilla-daemon [this message]
2022-02-21  6:55 ` bugzilla-daemon

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=bug-215621-206035-VuFAXSHQNL@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.