From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com,
mpe@ellerman.id.au
Cc: Florian Weimer <fweimer@redhat.com>, Jiri Slaby <jslaby@suse.cz>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: Kernel 4.15 lost set_robust_list support on POWER 9
Date: Tue, 06 Feb 2018 08:55:31 +1100 [thread overview]
Message-ID: <1517867731.2312.146.camel@au1.ibm.com> (raw)
In-Reply-To: <d5f533cf-bd97-794a-38e8-6b6d8c005023@linux.vnet.ibm.com>
On Mon, 2018-02-05 at 19:14 -0200, Mauricio Faria de Oliveira wrote:
> Nick, Michael,
+Aneesh.
> On 02/05/2018 10:48 AM, Florian Weimer wrote:
> > 7041 set_robust_list(0x7fff93dc3980, 24) = -1 ENOSYS (Function not
> > implemented)
>
> The regression was introduced by commit 371b8044 ("powerpc/64s:
> Initialize ISAv3 MMU registers before setting partition table").
>
> The problem is Radix MMU specific (does not occur with 'disable_radix'),
> and does not occur with that code reverted (ie do not set PIDR to zero).
>
> Do you see any reasons why?
> (wondering if at all related to access_ok() in include/asm/uaccess.h)
>
> with:
>
> # strace -e set_robust_list -f ./test
> set_robust_list(0x7fffa4b03910, 24) = -1 ENOSYS (Function not
> implemented)
> +++ exited with 1 +++
>
> # uname -r
> 4.15.0
>
> without:
>
> # strace -e set_robust_list -f ./test
> set_robust_list(0x7fff889c3910, 24) = 0
> +++ exited with 0 +++
>
> # uname -r
> 4.15.0.nopidr
next prev parent reply other threads:[~2018-02-05 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 12:48 Kernel 4.15 lost set_robust_list support on POWER 9 Florian Weimer
2018-02-05 12:59 ` Florian Weimer
2018-02-05 21:14 ` Mauricio Faria de Oliveira
2018-02-05 21:55 ` Benjamin Herrenschmidt [this message]
2018-02-06 1:06 ` Nicholas Piggin
2018-02-06 3:17 ` Aneesh Kumar K.V
2018-02-06 4:29 ` Nicholas Piggin
2018-02-06 13:17 ` Mauricio Faria de Oliveira
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=1517867731.2312.146.camel@au1.ibm.com \
--to=benh@au1.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fweimer@redhat.com \
--cc=jslaby@suse.cz \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mauricfo@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).