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=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 B6A51C388F9 for ; Sun, 8 Nov 2020 19:08:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 621E320731 for ; Sun, 8 Nov 2020 19:08:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604862480; bh=xHtls6lXIezqo3MY4JofvqKy4eD3Tg/zP3T1SVhh14M=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=Mc0l+hGlk02ssKkGaCYyKEFxA+cP7MhnCcWL196+E4q8w9/6oaFoZ9/7u9mcbWk4+ ZSd/befO43fh3MUIyy+XotfcDUIHqEy1LeEnJiKbNbEVMz0gbhx0iAhWQASZvsspU6 h4d36muF0PNyATDbI3J6mU3Y+Warpr7CRYCcrVuk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728873AbgKHTH6 (ORCPT ); Sun, 8 Nov 2020 14:07:58 -0500 Received: from mail.kernel.org ([198.145.29.99]:43626 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727570AbgKHTH6 (ORCPT ); Sun, 8 Nov 2020 14:07:58 -0500 Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6902B221FF for ; Sun, 8 Nov 2020 19:07:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604862477; bh=xHtls6lXIezqo3MY4JofvqKy4eD3Tg/zP3T1SVhh14M=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=OwQBk7ZmeUfBRnMBYMDC3sno96dtH68oH0mcOGWybDGRJ2FiCm75Pd11HFk47H/yj yStAq4g40HDRq1G96eWCFFZ+2GuX/1qkEjgF6w6934s8SVBAZbU7sE5DSRakMA+cil 1XGBFU401g4nzMjMZlv+BJaFsuvKrl6V5PEeHVSI= Received: by mail-wr1-f53.google.com with SMTP id c17so6502133wrc.11 for ; Sun, 08 Nov 2020 11:07:57 -0800 (PST) X-Gm-Message-State: AOAM531u4mmVrMqgxsx/NhS2F8e76c9NMCy/VFDPchWgJI8ZXgQC7wxe u+rb6/fuvAwPu/58bq88nlFtvwE2qnP6UlwN7aj5Rw== X-Google-Smtp-Source: ABdhPJzhIeYsh6ImqBo3MO13jFnDXj/3CxHcgilHtBOIs01JZKqESrAhAXBK5n9FiqSo+pApvOkp93Dmq6I76qqKv1w= X-Received: by 2002:adf:f0c2:: with SMTP id x2mr7511599wro.184.1604862475870; Sun, 08 Nov 2020 11:07:55 -0800 (PST) MIME-Version: 1.0 References: <20201108051730.2042693-1-dima@arista.com> In-Reply-To: <20201108051730.2042693-1-dima@arista.com> From: Andy Lutomirski Date: Sun, 8 Nov 2020 11:07:44 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 00/19] Add generic user_landing tracking To: Dmitry Safonov Cc: LKML , Dmitry Safonov <0x7f454c46@gmail.com>, Alexander Viro , Andrew Morton , Andy Lutomirski , Arnd Bergmann , Borislav Petkov , Catalin Marinas , Christophe Leroy , Guo Ren , "H. Peter Anvin" , Ingo Molnar , Oleg Nesterov , Russell King , Thomas Bogendoerfer , Thomas Gleixner , Vincenzo Frascino , Will Deacon , X86 ML , linux-arm-kernel , Albert Ou , "David S. Miller" , Palmer Dabbelt , Paul Walmsley , Linux FS Devel , Christian Borntraeger , Heiko Carstens , Vasily Gorbik , linux-s390 , sparclinux , "open list:MIPS" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov wrote: > > Started from discussion [1], where was noted that currently a couple of > architectures support mremap() for vdso/sigpage, but not munmap(). > If an application maps something on the ex-place of vdso/sigpage, > later after processing signal it will land there (good luck!) > > Patches set is based on linux-next (next-20201106) and it depends on > changes in x86/cleanups (those reclaim TIF_IA32/TIF_X32) and also > on my changes in akpm (fixing several mremap() issues). > > Logically, the patches set divides on: > - patch 1: cleanup for patches in x86/cleanups > - patches 2-11: cleanups for arch_setup_additional_pages() I like these cleanups, although I think you should stop using terms like "new-born". A task being exec'd is not newborn at all -- it's in the middle of a transformation. --Andy From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Date: Sun, 08 Nov 2020 19:07:44 +0000 Subject: Re: [PATCH 00/19] Add generic user_landing tracking Message-Id: List-Id: References: <20201108051730.2042693-1-dima@arista.com> In-Reply-To: <20201108051730.2042693-1-dima@arista.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Dmitry Safonov Cc: Catalin Marinas , Dmitry Safonov <0x7f454c46@gmail.com>, Oleg Nesterov , Guo Ren , "H. Peter Anvin" , sparclinux , Vincenzo Frascino , Will Deacon , linux-s390 , Vasily Gorbik , X86 ML , Russell King , Christophe Leroy , Christian Borntraeger , Ingo Molnar , "open list:MIPS" , Albert Ou , Arnd Bergmann , Heiko Carstens , Borislav Petkov , Alexander Viro , Andy Lutomirski , Paul Walmsley , Thomas Gleixner , linux-arm-kernel , Thomas Bogendoerfer , LKML , Palmer Dabbelt , Linux FS Devel , Andrew Morton , "David S. Miller" On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov wrote: > > Started from discussion [1], where was noted that currently a couple of > architectures support mremap() for vdso/sigpage, but not munmap(). > If an application maps something on the ex-place of vdso/sigpage, > later after processing signal it will land there (good luck!) > > Patches set is based on linux-next (next-20201106) and it depends on > changes in x86/cleanups (those reclaim TIF_IA32/TIF_X32) and also > on my changes in akpm (fixing several mremap() issues). > > Logically, the patches set divides on: > - patch 1: cleanup for patches in x86/cleanups > - patches 2-11: cleanups for arch_setup_additional_pages() I like these cleanups, although I think you should stop using terms like "new-born". A task being exec'd is not newborn at all -- it's in the middle of a transformation. --Andy 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=-4.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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 B1AA4C388F9 for ; Sun, 8 Nov 2020 19:08:28 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 47F8D20731 for ; Sun, 8 Nov 2020 19:08:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="eMbiwPyL"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="PyQhSvWt" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 47F8D20731 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=AAbw9P5Spr4ZCr2sE/TGw+8yxKKxpXqtHiMrmkfDXdU=; b=eMbiwPyL9cJZV7z8ABZZa65do fX2D2ShTXuSA5Dj1rg0fbE6BdkfWFqbuqC5kjKaty4Sjj8pLY41RvQ2C9s9XNr6KabzUjsL6X2zYE zHDfyRPvbG5hHrD0ewcKhCAiZKjctv/ieKv3a5uzHBq4ffT0HMrY4LRSPZ9ghYKy26AcIi1XyWlxx JeqKYpjUCmdRgkg3aB/1r3Zff52mFJiEYroeBsHJBSn3e6tzxgidI/6RKoc8FV9YxRN9KmyOPbg4W AXFtWFjkniTakD0RQa1NUWj9qs+9QFEWaQtXa9JyIfHmdatsjyJmBzTxydGiN6sA+x/+kth/ABtJ5 hTYDkMKXg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kbq2k-0006he-An; Sun, 08 Nov 2020 19:08:02 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kbq2g-0006gt-Ne for linux-arm-kernel@lists.infradead.org; Sun, 08 Nov 2020 19:08:00 +0000 Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CBF9F2222B for ; Sun, 8 Nov 2020 19:07:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604862478; bh=xHtls6lXIezqo3MY4JofvqKy4eD3Tg/zP3T1SVhh14M=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=PyQhSvWt72Htcg3N8GZXEEEl5gR4FJI6JEuNsNbSVIC5yZMIAKs1XQF1mLRB5jCwf J68uoFFpHEdLgW/eOxvZPg2K4I3vQuuKTqPUkM88ukz3L4M+jc3gIKz8i3j/HbRRQm +rQOnaPgYmSmHXUDr40yLQfsd65+yArsGzZXfWrY= Received: by mail-ed1-f45.google.com with SMTP id y15so6300947ede.11 for ; Sun, 08 Nov 2020 11:07:57 -0800 (PST) X-Gm-Message-State: AOAM5304Ip+FAQvb6PFYSpo1FxVTX+8LBRQuxLUWuNYCb/6nYLfdGRca oDrGk0WaKTBFEx0eEiKw9ko1h5+PLwO+zJUZbyvBbA== X-Google-Smtp-Source: ABdhPJzhIeYsh6ImqBo3MO13jFnDXj/3CxHcgilHtBOIs01JZKqESrAhAXBK5n9FiqSo+pApvOkp93Dmq6I76qqKv1w= X-Received: by 2002:adf:f0c2:: with SMTP id x2mr7511599wro.184.1604862475870; Sun, 08 Nov 2020 11:07:55 -0800 (PST) MIME-Version: 1.0 References: <20201108051730.2042693-1-dima@arista.com> In-Reply-To: <20201108051730.2042693-1-dima@arista.com> From: Andy Lutomirski Date: Sun, 8 Nov 2020 11:07:44 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 00/19] Add generic user_landing tracking To: Dmitry Safonov X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201108_140759_826766_1F2C98FA X-CRM114-Status: GOOD ( 19.47 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Catalin Marinas , Dmitry Safonov <0x7f454c46@gmail.com>, Oleg Nesterov , Guo Ren , "H. Peter Anvin" , sparclinux , Vincenzo Frascino , Will Deacon , linux-s390 , Vasily Gorbik , X86 ML , Russell King , Christophe Leroy , Christian Borntraeger , Ingo Molnar , "open list:MIPS" , Albert Ou , Arnd Bergmann , Heiko Carstens , Borislav Petkov , Alexander Viro , Andy Lutomirski , Paul Walmsley , Thomas Gleixner , linux-arm-kernel , Thomas Bogendoerfer , LKML , Palmer Dabbelt , Linux FS Devel , Andrew Morton , "David S. Miller" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov wrote: > > Started from discussion [1], where was noted that currently a couple of > architectures support mremap() for vdso/sigpage, but not munmap(). > If an application maps something on the ex-place of vdso/sigpage, > later after processing signal it will land there (good luck!) > > Patches set is based on linux-next (next-20201106) and it depends on > changes in x86/cleanups (those reclaim TIF_IA32/TIF_X32) and also > on my changes in akpm (fixing several mremap() issues). > > Logically, the patches set divides on: > - patch 1: cleanup for patches in x86/cleanups > - patches 2-11: cleanups for arch_setup_additional_pages() I like these cleanups, although I think you should stop using terms like "new-born". A task being exec'd is not newborn at all -- it's in the middle of a transformation. --Andy _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel