From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B30B3C2D0C3 for ; Mon, 30 Dec 2019 21:09:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 77262206DB for ; Mon, 30 Dec 2019 21:09:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="HqCV+yaq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727733AbfL3VJe (ORCPT ); Mon, 30 Dec 2019 16:09:34 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:41445 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727691AbfL3VJe (ORCPT ); Mon, 30 Dec 2019 16:09:34 -0500 Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id cc421e35; Mon, 30 Dec 2019 20:11:23 +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=6bUp3Unh4J5ntgEcnJwDilbtlDo=; b=HqCV+y aqge5F+06cKgztdUwKCaXLUh3/yblDQ4rDD3q3hZFy43Nw2+moMQGc5bLj1SkGgi frZecd04k7WC5zWIpOPYTz7LwnMirenNoImVd4pgnY+1ZqClE5TYDIPTms//4EJ9 Qr2QYRh2w5e23TB2+AX6yvB+uIhHxYPld5NTC/kfyh1iX1GPqcEhWMtJSay9/TlQ TRxAN24gygo5dRZPREc5R07+3xcoPDW9s1Km3CRZFyIBiJutNpK1Kiru5I7C74+I G9nQCIVfdmzMgl87jVYNa/cSnP3LGUhQYorZsC7sdXL1UoDhuJy4KA7Rd/FF+rhA uD+YZIoQJA+IfaIg== Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id fa0f9c9b (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Mon, 30 Dec 2019 20:11:23 +0000 (UTC) Received: by mail-oi1-f170.google.com with SMTP id i1so11478210oie.8; Mon, 30 Dec 2019 13:09:32 -0800 (PST) X-Gm-Message-State: APjAAAXV5b60Nw33JcRVh4nggeMk6YkAwguQndY3vvlrQf8uwZkuvNTq C58EAPFFFnriJ1sSRUXJYPrXgR1lnBz7/glcr0s= X-Google-Smtp-Source: APXvYqyuMCRQ4VcLihFnxz8xJ9iUYopeGnYSqitkoalUwep0OXon+FupZMuh+YSXdCyEyaIgYPN8EeXmHxElcAyDLgE= X-Received: by 2002:aca:2109:: with SMTP id 9mr351507oiz.119.1577740171616; Mon, 30 Dec 2019 13:09:31 -0800 (PST) MIME-Version: 1.0 References: <20191223130834.GA102399@zx2c4.com> <20191224135404.389039-1-Jason@zx2c4.com> In-Reply-To: From: "Jason A. Donenfeld" Date: Mon, 30 Dec 2019 22:09:20 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] mips: vdso: conditionalize 32-bit time functions on COMPAT_32BIT_TIME To: Arnd Bergmann Cc: "linux-kernel@vger.kernel.org" , "open list:BROADCOM NVRAM DRIVER" , Paul Burton , Vincenzo Frascino , Christian Brauner Content-Type: text/plain; charset="UTF-8" Sender: linux-mips-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-mips@vger.kernel.org On Mon, Dec 30, 2019 at 6:33 PM Arnd Bergmann wrote > Is this immediately before/after the syscall instruction or the > indirect function call? It's immediately after/before the call to the VDSO function itself. Next I'll try to instrument the VDSO to get closer to that syscall. I produced those reg dumps by hooking the page fault handler in the kernel to print them and then disabling aslr and sticking a `*(volatile int *)0 = 0;` in the code. Pretty gnarly.