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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09A76C433EF for ; Mon, 24 Jan 2022 09:29:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233761AbiAXJ3y (ORCPT ); Mon, 24 Jan 2022 04:29:54 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51496 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233884AbiAXJ3i (ORCPT ); Mon, 24 Jan 2022 04:29:38 -0500 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9015C06173B for ; Mon, 24 Jan 2022 01:29:37 -0800 (PST) Received: by mail-ed1-x536.google.com with SMTP id z22so55207239edd.12 for ; Mon, 24 Jan 2022 01:29:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=oC9HNsvbmipJaI7/3GLC383YFKywT6rDBqGjOn8JyvI=; b=nZAt5N2Jo6rWor+1/pb5P5RoORYE/ctNCULwQTr5Jjvv+zSvAW7uxDnILVSXZZ1RaV a7Zy/arNWBNllHfyoR5RmOie573vjoA5hzkuGzzAxYPu3wZbBDiOA7YW6TWgiKpmvDT9 fOI3Abq7XW7NvzAxv1QQ6uK9+BHwo4vCTQqhteysaA6oyqT9BINS2i04Iac888Ul7vuC 0zk2zmKiviRk6ZPAitr5GBCsEueY3KylmDSsiwlvrYOfUZKZHgrIT/xEWgxIwhdBDTQO 7ROp5m5paj9moyiPbYXY3PY6yL0y6inwtFEmNSOb7nMkmbeVMy6i1+OSkLgt7IQH5+En sKqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=oC9HNsvbmipJaI7/3GLC383YFKywT6rDBqGjOn8JyvI=; b=feJRQ0HRnNqZqU9nT4XrF75awMY4/PuESCwDTKNEC6Z2aa5XTZDqbEYbkFL8sjuBwz KWBWNLyvYrijTYc4dom/VRk0kQM8ZRuGVNAUMJgUMe8y1zmB49Aw8NcBTdy50wCTE50l IOsi1vowCyvanIt1sB5dpZrDYGUi04wl+yJS2X/YRgVheSdZNQU+6HSPnDKBHuPAhsrg psW6eXh6YW29eV35WZ99qK+9QC1yv3v9n60vElQPUL7Z4sAgqw+2ZoBSnQTKAtJzMWZm YI1678HaOtKr53z5nPqlHc4KjrVzu9vMwJPgVIhtqs/sXhlpGuW+qEkPJekv6FrJlnQt Q9SQ== X-Gm-Message-State: AOAM533FOifAnJI+4YIdCqNWqKTehtt+DEYfyuYDgM+8Dk+LZyIuRQEi LOnzMnbuuESbuW9uLNbL5jX8bA== X-Google-Smtp-Source: ABdhPJz/dWRJH3zsAQEGgsKWGUG7d9kYAfxghvUOyOChDrjndARlY2TJM66H2aMRp2nhXORS1trhmA== X-Received: by 2002:a05:6402:5190:: with SMTP id q16mr15192181edd.157.1643016576173; Mon, 24 Jan 2022 01:29:36 -0800 (PST) Received: from leoy-ThinkPad-X240s ([104.245.96.239]) by smtp.gmail.com with ESMTPSA id cf25sm3175786edb.63.2022.01.24.01.29.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Jan 2022 01:29:35 -0800 (PST) Date: Mon, 24 Jan 2022 17:29:28 +0800 From: Leo Yan To: "David S. Miller" , Jakub Kicinski , Leon Romanovsky , Mathieu Poirier , Suzuki K Poulose , Mike Leach , Alexander Shishkin , Jan Harkes , coda@cs.cmu.edu, Paul Moore , Eric Paris , Balbir Singh , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, codalist@coda.cs.cmu.edu, linux-audit@redhat.com Subject: Re: [PATCH v2 0/7] pid: Introduce helper task_is_in_root_ns() Message-ID: <20220124092928.GA1167041@leoy-ThinkPad-X240s> References: <20211208083320.472503-1-leo.yan@linaro.org> <20220112064046.GA3316542@leoy-ThinkPad-X240s> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220112064046.GA3316542@leoy-ThinkPad-X240s> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 12, 2022 at 02:40:47PM +0800, Leo Yan wrote: > Hi David, > > On Wed, Dec 08, 2021 at 04:33:13PM +0800, Leo Yan wrote: > > The kernel uses open code to check if a process is in root PID namespace > > or not in several places. > > > > Suggested by Suzuki, this patch set is to create a helper function > > task_is_in_init_pid_ns() to replace open code. > > > > This patch set has been applied on the mainline kernel and built for > > Arm64 kernel with enabling all relevant modules. > > I'd like sync for how to merging this patch set. Except patch 05/07, > all of other patches in this patch set have been received the reviewed > or acked tags. So could you pick up this patch set? > > Furthermore, we have another patch set "coresight: etm: Correct PID > tracing for non-root namespace" [1], which is dependent on the current > patch set and it has been Acked by Suzuki. > > I'd like to get opinions from David and CoreSight maintainers Mathieu > and Suzuki, should we merge the patch set [1] via David's tree as well > to avoid dependency issue, or prefer to merge it via CoreSight tree? > If David prefers the prior option, I can resend the patch set [1] with > looping David. Gentle ping, Dave. I verified the current patch set and CoreSight patch set, both can apply clearly on the latest mainline kernel (with last commit dd81e1c7d5fb "Merge tag 'powerpc-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux"). Thanks, Leo > [1] https://lore.kernel.org/lkml/20211213121323.1887180-1-leo.yan@linaro.org/ 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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 58FCBC433F5 for ; Mon, 24 Jan 2022 09:30:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=U+zy3LPxfLb65tH5bIFhJzCZYxIp/qF1CTjlf3XmDZw=; b=j1YjKuhvRUfdrs 5IKTltCWKMK2uFx5wLTC1n7CJnNlcgdwBXqIqrile+ljMHp36LTj5Xjac4iVSMztg5d24oThwx3CC Og0E28dvSfl+8bY5YmrAuOzk5sWvoD9EYBGFeo4pnkgMIYWrjDooFBUDwHrTCweXpW5DvouXbE0Kf fZ8F6wt6tqG1I1ZPP3jtGHmj74tAhBASW/ITccHbS/BD/XLAx9mLbE+e6anDU6Ne2VukwaQqrMvRQ JbGHj4GHjwRbzfB9rcQCLu+uDDg6dPejRMFAY7bN3lLSaSS4+/gxHD87CA9Dxw34Ne+hWs4zgkAsM V+BER+Ulr3yyjW3oDqUA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nBvfU-002nVS-WD; Mon, 24 Jan 2022 09:29:45 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nBvfO-002nUC-NT for linux-arm-kernel@lists.infradead.org; Mon, 24 Jan 2022 09:29:42 +0000 Received: by mail-ed1-x52e.google.com with SMTP id u18so41156518edt.6 for ; Mon, 24 Jan 2022 01:29:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=oC9HNsvbmipJaI7/3GLC383YFKywT6rDBqGjOn8JyvI=; b=nZAt5N2Jo6rWor+1/pb5P5RoORYE/ctNCULwQTr5Jjvv+zSvAW7uxDnILVSXZZ1RaV a7Zy/arNWBNllHfyoR5RmOie573vjoA5hzkuGzzAxYPu3wZbBDiOA7YW6TWgiKpmvDT9 fOI3Abq7XW7NvzAxv1QQ6uK9+BHwo4vCTQqhteysaA6oyqT9BINS2i04Iac888Ul7vuC 0zk2zmKiviRk6ZPAitr5GBCsEueY3KylmDSsiwlvrYOfUZKZHgrIT/xEWgxIwhdBDTQO 7ROp5m5paj9moyiPbYXY3PY6yL0y6inwtFEmNSOb7nMkmbeVMy6i1+OSkLgt7IQH5+En sKqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=oC9HNsvbmipJaI7/3GLC383YFKywT6rDBqGjOn8JyvI=; b=ObrjTeExeTOI7OzeA4YLvj1ehJm9tucXwlwwTWPiHDHGzBDMpaFNOGGqAUDxgtzfsk HkPmbPrWFKaxoa0/dF3ILmaDQenRIShP/DhvK280a8V0tNJBVk4J1R8fOc1m024aXfFO yqCjg6AiiT2pyAd4Q8rwoybk1elCFvNj61DwA06X5vobndAJc+K+XbpzfHJ8uhOiglj3 nyFRz2GyrKHcUUkmf6JHbfTWSkjryMO43Cw8dQIIM551tHIKFzqgXT1j6dBQBI4yRNkZ G0wlt4v5DGAZHTkctTKQETNHEAFYDrX46kRgMWMtJDE/d5Z50/CRdgAQqrXSciHZ0D79 pvKw== X-Gm-Message-State: AOAM532lZZyPDmi3gF69wnk3iNFzpwgq0TTFDwcqRzlsKoSNIbHc8FrL 2XxBVAVSdhIgDNiqOBwQwhUQ9w== X-Google-Smtp-Source: ABdhPJz/dWRJH3zsAQEGgsKWGUG7d9kYAfxghvUOyOChDrjndARlY2TJM66H2aMRp2nhXORS1trhmA== X-Received: by 2002:a05:6402:5190:: with SMTP id q16mr15192181edd.157.1643016576173; Mon, 24 Jan 2022 01:29:36 -0800 (PST) Received: from leoy-ThinkPad-X240s ([104.245.96.239]) by smtp.gmail.com with ESMTPSA id cf25sm3175786edb.63.2022.01.24.01.29.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Jan 2022 01:29:35 -0800 (PST) Date: Mon, 24 Jan 2022 17:29:28 +0800 From: Leo Yan To: "David S. Miller" , Jakub Kicinski , Leon Romanovsky , Mathieu Poirier , Suzuki K Poulose , Mike Leach , Alexander Shishkin , Jan Harkes , coda@cs.cmu.edu, Paul Moore , Eric Paris , Balbir Singh , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, codalist@coda.cs.cmu.edu, linux-audit@redhat.com Subject: Re: [PATCH v2 0/7] pid: Introduce helper task_is_in_root_ns() Message-ID: <20220124092928.GA1167041@leoy-ThinkPad-X240s> References: <20211208083320.472503-1-leo.yan@linaro.org> <20220112064046.GA3316542@leoy-ThinkPad-X240s> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220112064046.GA3316542@leoy-ThinkPad-X240s> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220124_012938_792451_B94326B4 X-CRM114-Status: GOOD ( 23.30 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Wed, Jan 12, 2022 at 02:40:47PM +0800, Leo Yan wrote: > Hi David, > > On Wed, Dec 08, 2021 at 04:33:13PM +0800, Leo Yan wrote: > > The kernel uses open code to check if a process is in root PID namespace > > or not in several places. > > > > Suggested by Suzuki, this patch set is to create a helper function > > task_is_in_init_pid_ns() to replace open code. > > > > This patch set has been applied on the mainline kernel and built for > > Arm64 kernel with enabling all relevant modules. > > I'd like sync for how to merging this patch set. Except patch 05/07, > all of other patches in this patch set have been received the reviewed > or acked tags. So could you pick up this patch set? > > Furthermore, we have another patch set "coresight: etm: Correct PID > tracing for non-root namespace" [1], which is dependent on the current > patch set and it has been Acked by Suzuki. > > I'd like to get opinions from David and CoreSight maintainers Mathieu > and Suzuki, should we merge the patch set [1] via David's tree as well > to avoid dependency issue, or prefer to merge it via CoreSight tree? > If David prefers the prior option, I can resend the patch set [1] with > looping David. Gentle ping, Dave. I verified the current patch set and CoreSight patch set, both can apply clearly on the latest mainline kernel (with last commit dd81e1c7d5fb "Merge tag 'powerpc-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux"). Thanks, Leo > [1] https://lore.kernel.org/lkml/20211213121323.1887180-1-leo.yan@linaro.org/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 278F7C433EF for ; Mon, 24 Jan 2022 14:02:14 +0000 (UTC) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-542-m8LQIPLDPuCxx-UDr3Md3Q-1; Mon, 24 Jan 2022 09:02:06 -0500 X-MC-Unique: m8LQIPLDPuCxx-UDr3Md3Q-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4F97F81C467; Mon, 24 Jan 2022 14:01:11 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7ED33708D9; Mon, 24 Jan 2022 14:01:09 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id B479E4BB7C; Mon, 24 Jan 2022 14:01:06 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 20O9TgF5019212 for ; Mon, 24 Jan 2022 04:29:42 -0500 Received: by smtp.corp.redhat.com (Postfix) id 7B2B1112132D; Mon, 24 Jan 2022 09:29:42 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast05.extmail.prod.ext.rdu2.redhat.com [10.11.55.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 76F0E112132C for ; Mon, 24 Jan 2022 09:29:39 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 643FD80029D for ; Mon, 24 Jan 2022 09:29:39 +0000 (UTC) Received: from mail-ed1-f44.google.com (mail-ed1-f44.google.com [209.85.208.44]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-441-xgKkL6bqOSaGcIns500gxA-1; Mon, 24 Jan 2022 04:29:37 -0500 X-MC-Unique: xgKkL6bqOSaGcIns500gxA-1 Received: by mail-ed1-f44.google.com with SMTP id p12so55432710edq.9 for ; Mon, 24 Jan 2022 01:29:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=oC9HNsvbmipJaI7/3GLC383YFKywT6rDBqGjOn8JyvI=; b=BRz5LQSH1Ev58zXelZrEKiCI/TO33I4QQoBsh2aMD0Bbr1rsM75LiL4dlXObIH6WZ1 gz0k6etpUvbuK0XsID+ttC8wGzmMEKXE/BIKpgsDHUNiZw9d7gjkz/BdpQNnOkg1Ice/ TxwuxZoTnoS0UPwcnikJQrWkNeAcRz+IDPN6UOvdndMOtWcTCI0PtJybFf+b97wYiIMI NzQT1Z1t7S90Ng/KC3flcR2Yj49Ol2vSxhNklPrWWwl6vB0xvtyaNlKgHR9cy/5LTIt0 lCM58gzHzLLn9p9v7YxF7X4LUPgfd1vtzY94+9bT4kwEajRS2mMAdQRPIg/ie5spdnH8 dmQw== X-Gm-Message-State: AOAM531m6AnXlrnum8CZK/a89+RUbcAwBATYQiicYwD7+6lku9Q12+oI VEUs4KPCap/5ZB3B9vPmMLkGwA== X-Google-Smtp-Source: ABdhPJz/dWRJH3zsAQEGgsKWGUG7d9kYAfxghvUOyOChDrjndARlY2TJM66H2aMRp2nhXORS1trhmA== X-Received: by 2002:a05:6402:5190:: with SMTP id q16mr15192181edd.157.1643016576173; Mon, 24 Jan 2022 01:29:36 -0800 (PST) Received: from leoy-ThinkPad-X240s ([104.245.96.239]) by smtp.gmail.com with ESMTPSA id cf25sm3175786edb.63.2022.01.24.01.29.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Jan 2022 01:29:35 -0800 (PST) Date: Mon, 24 Jan 2022 17:29:28 +0800 From: Leo Yan To: "David S. Miller" , Jakub Kicinski , Leon Romanovsky , Mathieu Poirier , Suzuki K Poulose , Mike Leach , Alexander Shishkin , Jan Harkes , coda@cs.cmu.edu, Paul Moore , Eric Paris , Balbir Singh , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, codalist@telemann.coda.cs.cmu.edu, linux-audit@redhat.com Subject: Re: [PATCH v2 0/7] pid: Introduce helper task_is_in_root_ns() Message-ID: <20220124092928.GA1167041@leoy-ThinkPad-X240s> References: <20211208083320.472503-1-leo.yan@linaro.org> <20220112064046.GA3316542@leoy-ThinkPad-X240s> MIME-Version: 1.0 In-Reply-To: <20220112064046.GA3316542@leoy-ThinkPad-X240s> X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-loop: linux-audit@redhat.com X-Mailman-Approved-At: Mon, 24 Jan 2022 09:01:04 -0500 X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=linux-audit-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Jan 12, 2022 at 02:40:47PM +0800, Leo Yan wrote: > Hi David, > > On Wed, Dec 08, 2021 at 04:33:13PM +0800, Leo Yan wrote: > > The kernel uses open code to check if a process is in root PID namespace > > or not in several places. > > > > Suggested by Suzuki, this patch set is to create a helper function > > task_is_in_init_pid_ns() to replace open code. > > > > This patch set has been applied on the mainline kernel and built for > > Arm64 kernel with enabling all relevant modules. > > I'd like sync for how to merging this patch set. Except patch 05/07, > all of other patches in this patch set have been received the reviewed > or acked tags. So could you pick up this patch set? > > Furthermore, we have another patch set "coresight: etm: Correct PID > tracing for non-root namespace" [1], which is dependent on the current > patch set and it has been Acked by Suzuki. > > I'd like to get opinions from David and CoreSight maintainers Mathieu > and Suzuki, should we merge the patch set [1] via David's tree as well > to avoid dependency issue, or prefer to merge it via CoreSight tree? > If David prefers the prior option, I can resend the patch set [1] with > looping David. Gentle ping, Dave. I verified the current patch set and CoreSight patch set, both can apply clearly on the latest mainline kernel (with last commit dd81e1c7d5fb "Merge tag 'powerpc-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux"). Thanks, Leo > [1] https://lore.kernel.org/lkml/20211213121323.1887180-1-leo.yan@linaro.org/ -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit