Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp6183511ybv; Tue, 18 Feb 2020 11:32:44 -0800 (PST) X-Google-Smtp-Source: APXvYqxgpnVg/KBowqdHreVdWO37ZaF3WbKoAjVp8eMXbRyeDNZQSQ5cKe0jXfbaNX+sPqvsVkOB X-Received: by 2002:a05:6830:22ee:: with SMTP id t14mr16581537otc.236.1582054363844; Tue, 18 Feb 2020 11:32:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582054363; cv=none; d=google.com; s=arc-20160816; b=I0ygBIIAGX2nelTtMcVHAIwx6SLAyduHNKgusm4O8V9dWA4w7EsZkjqqH++dbn3K7k yjENgo+GO1zxzHDnfoJYUlRSu/VFb8ffqMFRWCmTw5pAiJYFjRCc4DgKiogV/RZlHl0i z9fi6vFYwr+h0fFGX3v+xzokhoOsng6J8EssvVKDy2PkoEGVNdEj2kXq6Po8t+K5Cva1 XH49vOjiiQZP4gWH31Wa005RUWOgndPpUsQh78+gHSy0FT/Alrhpcq8nPljkS5VS2Bgn 66Y+wqCbf2/4DRjxnstSGqt20dE7xkc0SVw5b5MugsQjX8ZBfiBOiJVPbAe7WR/yVUk7 zMrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=LV+MVA27GmERT76AQSFW7+TDX7eGVtFvNiOU/nZfQ3g=; b=rPx01pscStT5sw+9Cvww4drIV+gXvwJS0AKOb8h9BQTSNtQT5m2JA2X/RHrdKvKLQ7 S5zF65kK3opD0gqynUbEFEo3ilwdypJAxvPgyCtXnahi5PY5rCOK7S6uLDGOLCiqCAlP b6g8zbvh94Q0ZxTn70to1IHyxJ+q0YNApPO0i62nWgivgWGgVZBSfM+UJKZDiE8MjCij XfztAN+vPZJ8JmpOf0Gde05dBe0H1K+1XNCi4e2Z+gyo9MlPvOvzC+5oo7ZNG5Q4jqmB gHJ947580V0jdT3tc0MSi92f5tgNsa84+VPP3Pq0Pbl1Tqb2dFGrnnpF6p+4W8sAdyxC kPMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (dns failure for signature) header.i=@infradead.org header.s=bombadil.20170209 header.b=JN0ihHEY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s9si8121327oij.78.2020.02.18.11.32.31; Tue, 18 Feb 2020 11:32:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=temperror (dns failure for signature) header.i=@infradead.org header.s=bombadil.20170209 header.b=JN0ihHEY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726609AbgBRTaz (ORCPT + 99 others); Tue, 18 Feb 2020 14:30:55 -0500 Received: from bombadil.infradead.org ([198.137.202.133]:50102 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726283AbgBRTaz (ORCPT ); Tue, 18 Feb 2020 14:30:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To: Subject:Sender:Reply-To:Content-ID:Content-Description; bh=LV+MVA27GmERT76AQSFW7+TDX7eGVtFvNiOU/nZfQ3g=; b=JN0ihHEYLrKtAzPlpc2c+kakEP AXp0XTtoT01qhyRVDWZ89g6HvK4L3jlP/8BV/rC0S8fh7kKrsJrsjge/9s1Tzbk85tLOvdP/dgdKC KtUyXXEhqmdV1Rrf6EvZnq+CRJTgsry5YplZrzyiHGG/bynzIJyBL9/5TNwzqv3HHAF7pfaEcP58h VltY5FDyp/4TIIzqDqlWeLyqpTIAiUI5xIVORPsbppF5tdlrOO+ytDl/tiJn9H+5iFXA0Kmnf3YJK KyyUiHIu8WC5g6+UIV+/C9tnyoGHjBAephjll88bh39KALFwj8Sac3OgF1HtOsV1W7mJJo4YQcNPn jOTObN7A==; Received: from [2601:1c0:6280:3f0::19c2] by bombadil.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1j48Zu-0007NA-EW; Tue, 18 Feb 2020 19:30:42 +0000 Subject: Re: [RFC PATCH] security: : fix all kernel-doc warnings To: Stephen Smalley , LKML , linux-security-module Cc: John Johansen , Kees Cook , Micah Morton , James Morris , "Serge E. Hallyn" , Paul Moore , Eric Paris , Casey Schaufler , Kentaro Takeda , Tetsuo Handa References: From: Randy Dunlap Message-ID: Date: Tue, 18 Feb 2020 11:30:40 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/18/20 6:03 AM, Stephen Smalley wrote: > On 2/16/20 2:08 AM, Randy Dunlap wrote: >> From: Randy Dunlap >> >> Fix all kernel-doc warnings in . >> Fixes the following warnings: >> >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'quotactl' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'quota_on' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'sb_free_mnt_opts' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'sb_eat_lsm_opts' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'sb_kern_mount' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'sb_show_options' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'sb_add_mnt_opt' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'd_instantiate' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'getprocattr' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'setprocattr' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'locked_down' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'perf_event_open' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'perf_event_alloc' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'perf_event_free' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'perf_event_read' not described in 'security_list_options' >> ../include/linux/lsm_hooks.h:1830: warning: Function parameter or member 'perf_event_write' not described in 'security_list_options' >> >> Signed-off-by: Randy Dunlap >> Cc: John Johansen >> Cc: Kees Cook >> Cc: Micah Morton >> Cc: James Morris >> Cc: "Serge E. Hallyn" >> Cc: linux-security-module@vger.kernel.org >> Cc: Paul Moore >> Cc: Stephen Smalley >> Cc: Eric Paris >> Cc: Casey Schaufler >> Cc: Kentaro Takeda >> Cc: Tetsuo Handa >> --- >> Notes: >> a. The location for some of these might need to be modified. >> b. 'locked_down' was just missing a final ':'. >> c. Added a new section: Security hooks for perf events. >> >>   include/linux/lsm_hooks.h |   36 +++++++++++++++++++++++++++++++++++- >>   1 file changed, 35 insertions(+), 1 deletion(-) >> >> --- lnx-56-rc1.orig/include/linux/lsm_hooks.h >> +++ lnx-56-rc1/include/linux/lsm_hooks.h >> @@ -136,6 +140,10 @@ >>    *    @sb superblock being remounted >>    *    @data contains the filesystem-specific data. >>    *    Return 0 if permission is granted. >> + * @sb_kern_mount: >> + *     Mount this @sb if allowed by permissions. >> + * @sb_show_options: >> + *     Show (print on @m) mount options for this @sb. >>    * @sb_umount: >>    *    Check permission before the @mnt file system is unmounted. >>    *    @mnt contains the mounted file system. > > Thanks for doing this.  Note that some of the existing kernel-doc comments for these hooks include a separate line describing each parameter (not just embedded in the function description) and a line describing the return value.  Is that optional for kernel-doc? Obviously what you have added here is an improvement, just wondering whether it suffices or needs further augmentation. Hi Stephen, The additional kernel-doc comments that you refer to are obviously Good to Have, but they are not required. I didn't feel comfortable or qualified to add all of that info, but if anyone wants to help/contribute, please do so. thanks. -- ~Randy