From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Paul Burton <paulburton@kernel.org>
Cc: linux-mips@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Christian Brauner <christian.brauner@canonical.com>
Subject: Re: vdso-related userspace crashes on 5.5 mips64
Date: Tue, 24 Dec 2019 14:37:09 +0100 [thread overview]
Message-ID: <CAHmME9qg8+xdM7Uo=XydwsOV27BWYK8fV44oimqiosBvH_-UDg@mail.gmail.com> (raw)
In-Reply-To: <20191223232945.a3sbzfj6uw2sokba@lantea.localdomain>
More details forthcoming, but I just bisected this to:
commit 942437c97fd9ff23a17c13118f50bd0490f6868c (refs/bisect/bad)
Author: Arnd Bergmann <arnd@arndb.de>
Date: Mon Jul 15 11:46:10 2019 +0200
y2038: allow disabling time32 system calls
At the moment, the compilation of the old time32 system calls depends
purely on the architecture. As systems with new libc based on 64-bit
time_t are getting deployed, even architectures that previously supported
these (notably x86-32 and arm32 but also many others) no longer depend on
them, and removing them from a kernel image results in a smaller kernel
binary, the same way we can leave out many other optional system calls.
More importantly, on an embedded system that needs to keep working
beyond year 2038, any user space program calling these system calls
is likely a bug, so removing them from the kernel image does provide
an extra debugging help for finding broken applications.
I've gone back and forth on hiding this option unless CONFIG_EXPERT
is set. This version leaves it visible based on the logic that
eventually it will be turned off indefinitely.
Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2019-12-24 13:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 13:08 vdso-related userspace crashes on 5.5 mips64 Jason A. Donenfeld
2019-12-23 21:44 ` Jason A. Donenfeld
2019-12-23 23:29 ` Paul Burton
2019-12-24 13:37 ` Jason A. Donenfeld [this message]
2019-12-30 15:58 ` Arnd Bergmann
2019-12-24 14:19 ` Jason A. Donenfeld
2019-12-24 13:54 ` [PATCH] mips: vdso: conditionalize 32-bit time functions on COMPAT_32BIT_TIME Jason A. Donenfeld
2019-12-30 11:57 ` Arnd Bergmann
2019-12-30 12:26 ` Jason A. Donenfeld
2019-12-30 12:34 ` Arnd Bergmann
2019-12-30 14:37 ` Jason A. Donenfeld
2019-12-30 15:10 ` Jason A. Donenfeld
2019-12-30 15:37 ` Arnd Bergmann
2019-12-30 15:39 ` Jason A. Donenfeld
2019-12-30 15:47 ` Arnd Bergmann
2019-12-30 15:58 ` Jason A. Donenfeld
2019-12-30 17:33 ` Arnd Bergmann
2019-12-30 21:09 ` Jason A. Donenfeld
2019-12-30 21:42 ` Jason A. Donenfeld
2019-12-31 16:14 ` Jason A. Donenfeld
2020-01-01 4:10 ` Paul Burton
2020-01-01 4:25 ` Paul Burton
2020-01-01 9:47 ` Jason A. Donenfeld
2020-01-01 9:47 ` Jason A. Donenfeld
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='CAHmME9qg8+xdM7Uo=XydwsOV27BWYK8fV44oimqiosBvH_-UDg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=christian.brauner@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--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).