From: Dmitry Safonov <0x7f454c46@gmail.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>,
Laurent Dufour <ldufour@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: VDSO ELF header
Date: Fri, 26 Mar 2021 18:54:24 +0000 [thread overview]
Message-ID: <e462ddff-c6c5-5c1b-a2f2-7352b85b332e@gmail.com> (raw)
In-Reply-To: <ec257b8b-d611-bbf4-86f3-bb0b758dbeaf@csgroup.eu>
On 3/26/21 6:40 PM, Christophe Leroy wrote:
>
>
> Le 26/03/2021 à 18:11, Dmitry Safonov a écrit :
>> On 3/26/21 5:07 PM, Christophe Leroy wrote:
>>> No, the problem is that user access has to be allowed for the flush()
>>>
>>> A hacky solution would be to call user_access_begin() , will test that
>>> later
>>
>> Yeah, cool.
>>
>> Will it be fine if I send the vvar patch with your Tested-by?
>>
>
> Tested-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Thank you!
I'll properly submit it shortly..
> With the user access fixed on the flush, it sigreturn_vdso selftest is a
> success. I'll send a patch for it in the coming days.
Nice!
> What is the status of your series which adds generic vdso_base tracking ?
Yeah, I was doing a new version of patches and I always was unsatisfied
by the result and stuck between "good" and "best" (more code rewriting).
And then had some other work to finish.
I'll try to finish and send it next week, thanks for pinging :-)
--
Dmitry
prev parent reply other threads:[~2021-03-26 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c45ae4f8-1cbc-c687-b6a2-9a431fafc85c@linux.ibm.com>
2021-03-25 16:46 ` VDSO ELF header Christophe Leroy
2021-03-25 16:56 ` Laurent Dufour
2021-03-25 19:02 ` Laurent Dufour
2021-03-26 10:46 ` Michael Ellerman
2021-03-26 10:50 ` Christophe Leroy
2021-03-26 15:13 ` Dmitry Safonov
2021-03-26 16:11 ` Christophe Leroy
2021-03-26 16:32 ` Dmitry Safonov
2021-03-26 17:07 ` Christophe Leroy
2021-03-26 17:11 ` Dmitry Safonov
2021-03-26 18:40 ` Christophe Leroy
2021-03-26 18:54 ` Dmitry Safonov [this message]
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=e462ddff-c6c5-5c1b-a2f2-7352b85b332e@gmail.com \
--to=0x7f454c46@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ldufour@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).