From: Paul Burton <paulburton@kernel.org>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: vincenzo.frascino@arm.com, paulburton@kernel.org, hns@goldelico.com
Cc: mips-creator-ci20-dev@googlegroups.com,
letux-kernel@openphoenux.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: Fix gettimeofday() in the vdso library
Date: Mon, 02 Dec 2019 11:48:19 -0800 [thread overview]
Message-ID: <5de56a84.1c69fb81.e0dc8.14af@mx.google.com> (raw)
In-Reply-To: <20191129143658.12224-1-vincenzo.frascino@arm.com>
Hello,
Vincenzo Frascino wrote:
> 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.
Applied to mips-fixes.
> commit 7d2aa4bb90f5
> https://git.kernel.org/mips/c/7d2aa4bb90f5
>
> Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
> Tested-by: H. Nikolaus Schaller <hns@goldelico.com> # CI20 with JZ4780
> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paulburton@kernel.org to report it. ]
prev parent reply other threads:[~2019-12-02 19:48 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
2019-11-29 15:09 ` H. Nikolaus Schaller
2019-12-02 19:48 ` Paul Burton [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=5de56a84.1c69fb81.e0dc8.14af@mx.google.com \
--to=paulburton@kernel.org \
--cc=hns@goldelico.com \
--cc=vincenzo.frascino@arm.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).