From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Paul Burton <paulburton@kernel.org>,
mips-creator-ci20-dev@googlegroups.com,
letux-kernel@openphoenux.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: Fix gettimeofday() in the vdso library
Date: Fri, 29 Nov 2019 14:58:52 +0000 [thread overview]
Message-ID: <0b64c6bb-ffc7-059d-3cb3-012092e0fcf0@arm.com> (raw)
In-Reply-To: <307717BD-3233-4313-BAA8-7431F4C78773@goldelico.com>
On 11/29/19 2:52 PM, H. Nikolaus Schaller wrote:
>
>> Am 29.11.2019 um 15:36 schrieb Vincenzo Frascino <vincenzo.frascino@arm.com>:
>>
>> The libc provides a discovery mechanism for vDSO library and its
>> symbols. When a symbol is not exposed by the vDSOs the libc falls back
>> on the system calls.
>>
>> With the introduction of the unified vDSO library on mips this behavior
>> is not honored anymore by the kernel in the case of gettimeofday().
>>
>> The issue has been noticed and reported due to a dhclient failure on the
>> CI20 board:
>>
>> root@letux:~# dhclient
>> ../../../../lib/isc/unix/time.c:200: Operation not permitted
>> root@letux:~#
>>
>> Restore the original behavior fixing gettimeofday() in the vDSO library.
>>
>> Cc: Paul Burton <paulburton@kernel.org>
>> Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
>> Testes-by: H. Nikolaus Schaller <hns@goldelico.com> # CI20 with JZ4780
> ^^^ funny typo... -> Tested-by:
Ops, I copy-pasted it from your email ;) Can't trust you ;)
--
Regards,
Vincenzo
next prev parent reply other threads:[~2019-11-29 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:36 [PATCH] mips: Fix gettimeofday() in the vdso library Vincenzo Frascino
2019-11-29 14:52 ` H. Nikolaus Schaller
2019-11-29 14:58 ` Vincenzo Frascino [this message]
2019-11-29 15:09 ` H. Nikolaus Schaller
2019-12-02 19:48 ` Paul Burton
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=0b64c6bb-ffc7-059d-3cb3-012092e0fcf0@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mips-creator-ci20-dev@googlegroups.com \
--cc=paulburton@kernel.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.