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 AC1B6C433FE for ; Wed, 12 Jan 2022 06:40:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351020AbiALGk6 (ORCPT ); Wed, 12 Jan 2022 01:40:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237188AbiALGk4 (ORCPT ); Wed, 12 Jan 2022 01:40:56 -0500 Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 67CF0C061748 for ; Tue, 11 Jan 2022 22:40:55 -0800 (PST) Received: by mail-ed1-x534.google.com with SMTP id q25so5857858edb.2 for ; Tue, 11 Jan 2022 22:40:55 -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=j6hbyKol68wFX5iiymhuEQsHgpNKkmkI3FMm7bj3TOM=; b=DEtq4nScoRmZpHDPIBFDzULWTmc5oEnWu0HWl9mQoRoTBM/ad+z67adCChiy1HP+pi Mjg76DatHzF73HgPRTkNFeVunycvIIrnPHK779ME6ig3sk4t9yTZcHn++pQulQo1u6Og DbWzyLfYG5f49VrhQgdqFb/MuIFgl/WUeFAQTGJl/LFgzVifoBOEP2obm0yPedSGnpyp Pq5ybK7XZ5Da8x4DaO5dOZmka175e9kebZLXISJdscKlODyPDME40gTkt+O3Uk4IFQx6 zVUXDFXfWJ0mE6jE2Jmx7lUJt1hQmAE/k2d9KoTKwEwgt8g5+h/xsBMjs4qSLFRHaPwu IdGQ== 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=j6hbyKol68wFX5iiymhuEQsHgpNKkmkI3FMm7bj3TOM=; b=sVpDiwgTg2X6wbNlOuR9VTO40OqmJ03eZ0R8a4+8Y2B+BumuaiUa+yxn/h/9Z8Nx0J k2Ydst2ZjnJ5493SpH233+igmWINtXBsRXtQzbQqGicWPex+AKNUydqvsfq6wEqi0w/m XKZw3SujXkjNQfRY2p73nc67sLA+1GUU6KZN1RZw5gzF4O918u/gf73q27UqRIVctUPl 4x4lodcpO/yK283D/cRoBV+nrJSJ0FpODKwVMTFY4eITxiAWIx+6IqXKk933CDLsw45t u25xLYizSd7ySIfzy1x45qADfZWZ5/hl1oR2nw7K63qWNXCx6oNlXI4i9801jdFZ1648 NSrg== X-Gm-Message-State: AOAM533Loxy5IYbzcsGQSVUoD8PtXtmhAYLvTHN9kqv0p5yM1+IkPBmO EK0/lVvNhcMXzUG4OTrjiohd2g== X-Google-Smtp-Source: ABdhPJxFACxwQqohWAwzNyIFzdza3Go5zCu+23kAyqd4VttcVfMxPX4biC1GqarDCqok0lezkQ4qEQ== X-Received: by 2002:a50:d6d5:: with SMTP id l21mr7486410edj.69.1641969653736; Tue, 11 Jan 2022 22:40:53 -0800 (PST) Received: from leoy-ThinkPad-X240s ([104.245.96.239]) by smtp.gmail.com with ESMTPSA id ck3sm1892109edb.36.2022.01.11.22.40.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 22:40:53 -0800 (PST) Date: Wed, 12 Jan 2022 14:40:47 +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: <20220112064046.GA3316542@leoy-ThinkPad-X240s> References: <20211208083320.472503-1-leo.yan@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211208083320.472503-1-leo.yan@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Leo [1] https://lore.kernel.org/lkml/20211213121323.1887180-1-leo.yan@linaro.org/