Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp7605159ybl; Tue, 24 Dec 2019 05:38:33 -0800 (PST) X-Google-Smtp-Source: APXvYqzBJBUDXa0hdDXEyDTHEmGN7hnqZdtHjd3htDcd5kWHTvpDH1/nPlwcakcVuloeWW7HQXiz X-Received: by 2002:aca:1e11:: with SMTP id m17mr188044oic.5.1577194713153; Tue, 24 Dec 2019 05:38:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577194713; cv=none; d=google.com; s=arc-20160816; b=tjyCsBMUFBz5NWi3qpXht4VqCz7Gk/5N8iDV4yKL6BE1HDMCALI6q40cWcl38jeLyO O0/XUjkCfKKgmn8/+Ra/q4Xw576P1FhISLcDFBuTg4bAUt/O4Ej3JIPhi9U5QACVQDmt ys1ZWV2qe4/bleB96v09hVNKclfI0ezcljBFDnU7mWkrUoK3bWMAxv9ZyYyAqdtbVkmA RGkxSD4tl80olrViDZT6krRKLGz1HHtOQhj+yp04kT0WJFXQHVN2c06zA7lIHY37bxVo T6OOhrK/Pjnz/EQsmauq8HcryNto0qJQ+Dv+CHTfo0bI+rFWGMmHrF9BsuG/k72Rwzda vcHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=RPBO/ujTAib2eH2IBBUioCEUFkA64I2/XXpjF8UuvEk=; b=Z003GG5L6xhDh/4fJCHCiFAC/Uro2CaMRXlLu6nPvfA+7yRRrMfW8Z4LOzbyW82eUN WwAq5t1lC5opxL6a8duKJpsslvvKQyuIhn0avEswoeoIuathg+f15APZ8U6s/ZK1uMLJ mz8u7PTOsC+If3v5MfKhkN10KtCemPTKk9nTMzYPedL85/25bqWTlhd02ofLP8Has5g1 QpwueuCkdEk6DTe9xD4S3LFyXFxVpRs1e9bHRwEyvHGt09W9DdQGO+g6Q3qocXmPoKFe LdsmalP/N6NBqgHaCErlYpIGpqTEViVIDLXd2PqzonQIj3+t+MOpvBYqzKUPhb04KWLA TX0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=WDGKIy18; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q9si10202044oij.125.2019.12.24.05.38.21; Tue, 24 Dec 2019 05:38:33 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=WDGKIy18; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726283AbfLXNhY (ORCPT + 99 others); Tue, 24 Dec 2019 08:37:24 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:55361 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726171AbfLXNhY (ORCPT ); Tue, 24 Dec 2019 08:37:24 -0500 Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id fd6f0d0b; Tue, 24 Dec 2019 12:40:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=mail; bh=gEFNMUQrn8pc8q7jFRWms1pimpI=; b=WDGKIy 18ogApN3mCCt1ei3p//f+ODjeMeU3WEm0RkKAoGy+68nFuZxrzurmv9TREQ425T7 RpVjDmc/IYlHa50bSodtQ1kzbbyvtzOAaJUxRv2S6WRD9Yx1cAgIQ1kS50EG9Y8T j9bEHGao9dOOlL5dAdEruj1Lt9lc52YYE0z42eDdJjNWIC8uai8tFCiQP7Zs1PE6 iyzGPbinUxXEOJzWv2FyzmTjAHvC/iLj3JJpgebaY5ibaCJZHuNDx1w1y8G3OODu rNhdtcv/gJa24gEDPbAimM7jGpJSZmE3OY2yDJ1LmpBNEpKLB6HkPoxBHQX1lfWR LwJEsshUu/l/k2tg== Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 9ce5fc91 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 24 Dec 2019 12:40:00 +0000 (UTC) Received: by mail-ot1-f50.google.com with SMTP id k16so21816731otb.2; Tue, 24 Dec 2019 05:37:21 -0800 (PST) X-Gm-Message-State: APjAAAUcN+P8AMsvGeAXADpuXyuqubZ56t0wGrXxH9CB7vHeOeSbRvVA Drdbc9eDdMRWpHu7B0pLTiVmE+LgK44SLlASnUg= X-Received: by 2002:a05:6830:1141:: with SMTP id x1mr39295818otq.120.1577194640368; Tue, 24 Dec 2019 05:37:20 -0800 (PST) MIME-Version: 1.0 References: <20191223130834.GA102399@zx2c4.com> <20191223232945.a3sbzfj6uw2sokba@lantea.localdomain> In-Reply-To: <20191223232945.a3sbzfj6uw2sokba@lantea.localdomain> From: "Jason A. Donenfeld" Date: Tue, 24 Dec 2019 14:37:09 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: vdso-related userspace crashes on 5.5 mips64 To: Paul Burton Cc: linux-mips@vger.kernel.org, LKML , Arnd Bergmann , Vincenzo Frascino , Christian Brauner Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org More details forthcoming, but I just bisected this to: commit 942437c97fd9ff23a17c13118f50bd0490f6868c (refs/bisect/bad) Author: Arnd Bergmann 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 Signed-off-by: Arnd Bergmann