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=-12.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 64999C64E90 for ; Wed, 2 Dec 2020 00:06:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 220B62223C for ; Wed, 2 Dec 2020 00:06:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727331AbgLBAFz (ORCPT ); Tue, 1 Dec 2020 19:05:55 -0500 Received: from mail.kernel.org ([198.145.29.99]:56566 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726997AbgLBAFy (ORCPT ); Tue, 1 Dec 2020 19:05:54 -0500 X-Gm-Message-State: AOAM5319TBglYyyZU5WTD8/6DGU/PFB4hBeXws8cNwTQw4CouWtHcxWo HRA+q+fr/lhyswlpF33S/q/zjfFbx1JwMYcH49tjGg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606867514; bh=mMmeqR8hm5LCOImSwkBcFK9EfPV0jMKdTiPbXqm0H9U=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=YXKNYXDqKx7uMuuKII51Blau1OyoYZmaGq2xiWFqRdbh4+0ttupnaaWnGQHRnEM41 smeEHSLyi14sV+mrjmryB3SZOUZjPEsdIHqPpW5U11RoLLQn/z9ywK8n8ai3McEYK0 A6Kqi9oXU0ufUDniPBUM+Kt+zze/tgSxpQQREg1M= X-Google-Smtp-Source: ABdhPJxGs1zQTY53PW9S7f3409gymiEDgGfegriuR8Dl9nvI8iqGiqqobv4k0ao5I32uvxBf3l/glympCI0ntbMurBU= X-Received: by 2002:adf:f0c2:: with SMTP id x2mr7014860wro.184.1606867512366; Tue, 01 Dec 2020 16:05:12 -0800 (PST) MIME-Version: 1.0 References: <20201127193238.821364-1-krisman@collabora.com> In-Reply-To: <20201127193238.821364-1-krisman@collabora.com> From: Andy Lutomirski Date: Tue, 1 Dec 2020 16:04:59 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v8 0/7] Syscall User Dispatch To: Gabriel Krisman Bertazi Cc: Andrew Lutomirski , Thomas Gleixner , Kees Cook , Paul Gofman , Christian Brauner , Peter Zijlstra , Matthew Wilcox , Shuah Khan , LKML , Linux API , "open list:KERNEL SELFTEST FRAMEWORK" , X86 ML , kernel@collabora.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 27, 2020 at 11:32 AM Gabriel Krisman Bertazi wrote: > > Hi, > > This is v8 of syscall user dispatch. Last version got some acks but > there was one small documentation fix I wanted to do, as requested by > Florian. This also addresses the commit message fixup Peter requested. > > The only actual code change from v7 is solving a trivial merge conflict > I myself created with the entry code fixup I made week and with > something else in the TIP tree. > > I also shared this with glibc and there wasn't any complaints other than > the matter about user-notif vs. siginfo, which was discussed in v7 and > the understanding is that it is not necessary now and can be added > later, if needed, on the same infrastructure without a new api. > > I'm not sure about TIP the rules, but is it too late to be queued for > the next merge window? I'd love to have this in 5.11 if possible, since > it has been flying for quite a while. > Other than my little nitpick about on_syscall_dispatch(), the whole series is: Reviewed-by: Andy Lutomirski