Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp3129421rwb; Fri, 9 Dec 2022 10:17:10 -0800 (PST) X-Google-Smtp-Source: AA0mqf7M5YiXY/A/O4f7VCZAvygkI+p4rJPJRi1NE2S077uSJ3zxG9ZzbJXeUlzjhqYuPytOuq0S X-Received: by 2002:a05:6a21:e310:b0:aa:83b9:fe5b with SMTP id cb16-20020a056a21e31000b000aa83b9fe5bmr8943129pzc.23.1670609830600; Fri, 09 Dec 2022 10:17:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670609830; cv=none; d=google.com; s=arc-20160816; b=wWJp7Weu7p6S1hDGE9rKX974fMDmP2hcXJZo2TMGKds9IBrOoy+EtPCWhuNXl4WB5d A6GziryvnQMJXYWrnWlncwoNZAtltN15VBfzemU2Vo/VnMBCD2nYQStcH+PAL8cBwetR bf4Yna9n6XM0QrbVTG0nYmTGZF/I5MJH2JJKbaH1Y7joABmtL8SWWdt5gycYXdw1gBlG +7jYt4SDu1A5Z99NQui1aGzP5PMhE1PDxkXlp51nYUdomlYI+8zJCEDnYzJ7+56wFdrL lLcDsTjdvpXPcCIiKlL3PmjTJFGqGmSbiQwzzfbvQ3ROaImxAFP2ZlBhI9f2c7U2Aot0 Yawg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=ZFm1mHWqGIzhe+rb1eJUuw0XvgXopgBYaEtqlXPVfz0=; b=RooQQMQweLiS5GdnkkQaaAQzIDF7Apdr844g+hmyJ4fQUE1E95iQHj/ZYQ9w7VDg9P C8A7R7UXbIJp9lDmUkuto4eBt1iNioyF19suxbj1IIuk37Vfz/yrz35UGjNEciFMyvYu g/7KGLyGfxBve3Llbx4SNH0UKn0+qsPBYj0zrnDXHR33pa4eMUSzOyQAVm+lbuoYEwbz HNDYelFU0mBcbTwjHcF0zYAheMyT50p6GqN0jvQuBCKENNYb2+ziMUQ8dZ9DIhyJK6iL hX0FDUztmOzvhmUN5GiFjhLBdWP6CJZxNrEFyXuzT1Rzvw0Uni6g1BRGCEhYbruvXyDI YZRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@paul-moore-com.20210112.gappssmtp.com header.s=20210112 header.b="hKQY4J/p"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l34-20020a635722000000b0047850dc6cdasi1991032pgb.116.2022.12.09.10.17.00; Fri, 09 Dec 2022 10:17:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@paul-moore-com.20210112.gappssmtp.com header.s=20210112 header.b="hKQY4J/p"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230178AbiLIRlz (ORCPT + 74 others); Fri, 9 Dec 2022 12:41:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230157AbiLIRls (ORCPT ); Fri, 9 Dec 2022 12:41:48 -0500 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 508E88D182 for ; Fri, 9 Dec 2022 09:41:44 -0800 (PST) Received: by mail-pl1-x62c.google.com with SMTP id jn7so5595895plb.13 for ; Fri, 09 Dec 2022 09:41:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZFm1mHWqGIzhe+rb1eJUuw0XvgXopgBYaEtqlXPVfz0=; b=hKQY4J/pRm6CWAMtVWIamF1UR1S5ytG4Q0dHLvMKrbYlyUycxPoWBv9Nvh4aE85080 MWzlNOjWwFO925vt2GUNcS/9BsF/orNKSvNrMiJHpxpXZP/fsRzj2P95wFaUt+bI8jC4 HKRo33TkZwcuRzKPFMZ/Et6g/CaKhLpD6XEakiYyIPyXFiTK9hpXRej8x43ZakzvAdnu cc2uWLlT8LDekFoJ0DodzV9KIG5fEqwrWeJJE5FFSWTew4hhwEfHkkmQuMbzZJ1BkUaR /AoTD8PntICNQW80RuAfzK6ZOG6OUwhJeXxnL+Z8dW9hRID7YD/0yMk+1SSU/RwDz4Iv IAeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZFm1mHWqGIzhe+rb1eJUuw0XvgXopgBYaEtqlXPVfz0=; b=PYo2/Ybrad/Kk+CUNznHSPuAqvUypucXniETTVBGP34hlQkqjMbXWscEhujhcVWS4l jmZOEedA4nDtUnqXNSpa4atxfCCcWTytTp8UdCIf52Op5/W+9nqMxd95HKi50OwxBnR5 p1rmhC03M9R7ypG1raRI3qq+wFmIdDKaaU3TxM7rB0O5vMX/aCCAxGtVY6i5q4NmPD3W aEBgNst93z1g/xM5kdOZOd0beJzv4Xy0I2GxgezotimIo8D7CxdzNGZvfDblXf85dpDS 7MsJYY1TQOPkxoWqWcRyOGzNbh8yikIoJz2WGP59BDWZftc1DUPaqxoQXvley5dcTDv7 wVcw== X-Gm-Message-State: ANoB5pnSr5s/pETTMhle5882v4yDa+E+6/3i6QYGZo/Na6RsG/psalQR nkW7qgQKGy9lLJko5ZFYpyazEbY+KlgOLfoK78QZ7HOmfszr X-Received: by 2002:a17:90b:2743:b0:20d:4173:faf9 with SMTP id qi3-20020a17090b274300b0020d4173faf9mr108635116pjb.147.1670607703640; Fri, 09 Dec 2022 09:41:43 -0800 (PST) MIME-Version: 1.0 References: <20221209082936.892416-1-roberto.sassu@huaweicloud.com> <20221209082936.892416-2-roberto.sassu@huaweicloud.com> In-Reply-To: <20221209082936.892416-2-roberto.sassu@huaweicloud.com> From: Paul Moore Date: Fri, 9 Dec 2022 12:41:32 -0500 Message-ID: Subject: Re: [PATCH 2/2] doc: Fix fs_context_parse_param description in mount_api.rst To: Roberto Sassu Cc: corbet@lwn.net, casey@schaufler-ca.com, omosnace@redhat.com, john.johansen@canonical.com, kpsingh@kernel.org, bpf@vger.kernel.org, linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Roberto Sassu Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 9, 2022 at 3:30 AM Roberto Sassu wrote: > > From: Roberto Sassu > > Align with the description of fs_context_parse_param in lsm_hooks.h, which > seems the right one according to the code. > > Signed-off-by: Roberto Sassu > --- > Documentation/filesystems/mount_api.rst | 9 ++++----- > 1 file changed, 4 insertions(+), 5 deletions(-) I'm going to leave this patch as a "hold" for right now. The existing text is arguably not great, but I'm not really in love with the replacement text taken from the LSM hook comments; given the merge window opens in a couple of days, we don't have much time to fiddle with the wording so let's just hold this for a little bit. These comment corrections (which are very welcome!) have also reminded me that we really should move the hook comment blocks out of the header file and into security.c like every other kernel function. This should help increase their discoverability while also making it easier to maintain the comments over time. I'm going to post a first pass at this as soon as the merge window closes, and once that is done we can do further work to cleanup the descriptions and add more detail (including notes both for the other kernel subsystems that call the hooks and the LSM devs who provide implementations). -- paul-moore.com