All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Igor Stoppa <igor.stoppa@huawei.com>
Cc: willy@infradead.org, rdunlap@infradead.org, corbet@lwn.net,
	keescook@chromium.org, mhocko@kernel.org, labbott@redhat.com,
	jglisse@redhat.com, hch@infradead.org, cl@linux.com,
	linux-security-module@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 4/6] Protectable Memory
Date: Mon, 12 Feb 2018 17:31:57 +0200	[thread overview]
Message-ID: <20180212153156.GF20737@rapoport-lnx> (raw)
In-Reply-To: <68edadf0-2b23-eaeb-17de-884032f0b906@huawei.com>

On Mon, Feb 12, 2018 at 03:41:57PM +0200, Igor Stoppa wrote:
> 
> 
> On 12/02/18 14:53, Mike Rapoport wrote:
> > 'scripts/kernel-doc -v -none 
> 
> That has a quite interesting behavior.
> 
> I run it on genalloc.c while I am in the process of adding the brackets
> to the function names in the kernel-doc description.
> 
> The brackets confuse the script and it fails to output the name of the
> function in the log:
> 
> lib/genalloc.c:123: info: Scanning doc for get_bitmap_entry
> lib/genalloc.c:139: info: Scanning doc for
> lib/genalloc.c:152: info: Scanning doc for
> lib/genalloc.c:164: info: Scanning doc for

 
> 
> The first function does not have the brackets.
> The others do. So what should I do with the missing brackets?
> Add them, according to the kernel docs, or leave them out?

Seems that kernel-doc does not consider () as a valid match for the
identifier :)
 
Can you please check with the below patch?

> I'd lean toward adding them.
> 
> --
> igor
 
-- 
Sincerely yours,
Mike.

>From 35255bc2d7d2a63be4f78a7bf4eec83ab0dc4f3f Mon Sep 17 00:00:00 2001
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
Date: Mon, 12 Feb 2018 17:19:04 +0200
Subject: [PATCH] scripts: kernel_doc: fixup reporting of function identifiers

When function description includes brackets after the function name as
suggested by Documentation/doc-guide/kernel-doc, the kernel-doc script
omits the function name from "Scanning doc for" report.
Extending match for identifier name with optional brackets fixes this
issue.

Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
---
 scripts/kernel-doc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index fee8952037b1..a6a9a8ef116c 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -1873,7 +1873,7 @@ sub process_file($) {
 	    }
 	    elsif (/$doc_decl/o) {
 		$identifier = $1;
-		if (/\s*([\w\s]+?)\s*-/) {
+		if (/\s*([\w\s]+?)(\(\))?\s*-/) {
 		    $identifier = $1;
 		}
 
-- 
2.7.4

WARNING: multiple messages have this Message-ID (diff)
From: rppt@linux.vnet.ibm.com (Mike Rapoport)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 4/6] Protectable Memory
Date: Mon, 12 Feb 2018 17:31:57 +0200	[thread overview]
Message-ID: <20180212153156.GF20737@rapoport-lnx> (raw)
In-Reply-To: <68edadf0-2b23-eaeb-17de-884032f0b906@huawei.com>

On Mon, Feb 12, 2018 at 03:41:57PM +0200, Igor Stoppa wrote:
> 
> 
> On 12/02/18 14:53, Mike Rapoport wrote:
> > 'scripts/kernel-doc -v -none 
> 
> That has a quite interesting behavior.
> 
> I run it on genalloc.c while I am in the process of adding the brackets
> to the function names in the kernel-doc description.
> 
> The brackets confuse the script and it fails to output the name of the
> function in the log:
> 
> lib/genalloc.c:123: info: Scanning doc for get_bitmap_entry
> lib/genalloc.c:139: info: Scanning doc for
> lib/genalloc.c:152: info: Scanning doc for
> lib/genalloc.c:164: info: Scanning doc for

 
> 
> The first function does not have the brackets.
> The others do. So what should I do with the missing brackets?
> Add them, according to the kernel docs, or leave them out?

Seems that kernel-doc does not consider () as a valid match for the
identifier :)
 
Can you please check with the below patch?

> I'd lean toward adding them.
> 
> --
> igor
 
-- 
Sincerely yours,
Mike.

>From 35255bc2d7d2a63be4f78a7bf4eec83ab0dc4f3f Mon Sep 17 00:00:00 2001
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
Date: Mon, 12 Feb 2018 17:19:04 +0200
Subject: [PATCH] scripts: kernel_doc: fixup reporting of function identifiers

When function description includes brackets after the function name as
suggested by Documentation/doc-guide/kernel-doc, the kernel-doc script
omits the function name from "Scanning doc for" report.
Extending match for identifier name with optional brackets fixes this
issue.

Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
---
 scripts/kernel-doc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index fee8952037b1..a6a9a8ef116c 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -1873,7 +1873,7 @@ sub process_file($) {
 	    }
 	    elsif (/$doc_decl/o) {
 		$identifier = $1;
-		if (/\s*([\w\s]+?)\s*-/) {
+		if (/\s*([\w\s]+?)(\(\))?\s*-/) {
 		    $identifier = $1;
 		}
 
-- 
2.7.4


--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Igor Stoppa <igor.stoppa@huawei.com>
Cc: willy@infradead.org, rdunlap@infradead.org, corbet@lwn.net,
	keescook@chromium.org, mhocko@kernel.org, labbott@redhat.com,
	jglisse@redhat.com, hch@infradead.org, cl@linux.com,
	linux-security-module@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 4/6] Protectable Memory
Date: Mon, 12 Feb 2018 17:31:57 +0200	[thread overview]
Message-ID: <20180212153156.GF20737@rapoport-lnx> (raw)
In-Reply-To: <68edadf0-2b23-eaeb-17de-884032f0b906@huawei.com>

On Mon, Feb 12, 2018 at 03:41:57PM +0200, Igor Stoppa wrote:
> 
> 
> On 12/02/18 14:53, Mike Rapoport wrote:
> > 'scripts/kernel-doc -v -none 
> 
> That has a quite interesting behavior.
> 
> I run it on genalloc.c while I am in the process of adding the brackets
> to the function names in the kernel-doc description.
> 
> The brackets confuse the script and it fails to output the name of the
> function in the log:
> 
> lib/genalloc.c:123: info: Scanning doc for get_bitmap_entry
> lib/genalloc.c:139: info: Scanning doc for
> lib/genalloc.c:152: info: Scanning doc for
> lib/genalloc.c:164: info: Scanning doc for

 
> 
> The first function does not have the brackets.
> The others do. So what should I do with the missing brackets?
> Add them, according to the kernel docs, or leave them out?

Seems that kernel-doc does not consider () as a valid match for the
identifier :)
 
Can you please check with the below patch?

> I'd lean toward adding them.
> 
> --
> igor
 
-- 
Sincerely yours,
Mike.

  reply	other threads:[~2018-02-12 15:31 UTC|newest]

Thread overview: 146+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11  3:19 [RFC PATCH v15 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-02-11  3:19 ` Igor Stoppa
2018-02-11  3:19 ` Igor Stoppa
2018-02-11  3:19 ` Igor Stoppa
2018-02-11  3:19 ` [PATCH 1/6] genalloc: track beginning of allocations Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11 12:24   ` Mike Rapoport
2018-02-11 12:24     ` Mike Rapoport
2018-02-11 12:24     ` Mike Rapoport
2018-02-12 11:17     ` Igor Stoppa
2018-02-12 11:17       ` Igor Stoppa
2018-02-12 11:17       ` Igor Stoppa
2018-02-12 11:17       ` Igor Stoppa
2018-02-12 11:36       ` Mike Rapoport
2018-02-12 11:36         ` Mike Rapoport
2018-02-12 11:36         ` Mike Rapoport
2018-02-13  0:43   ` kbuild test robot
2018-02-13  0:43     ` kbuild test robot
2018-02-13  0:43     ` kbuild test robot
2018-02-11  3:19 ` [PATCH 2/6] genalloc: selftest Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11 20:22   ` Philippe Ombredanne
2018-02-11 20:22     ` Philippe Ombredanne
2018-02-11 20:22     ` Philippe Ombredanne
2018-02-11 20:27     ` Randy Dunlap
2018-02-11 20:27       ` Randy Dunlap
2018-02-11 20:27       ` Randy Dunlap
2018-02-11 21:01       ` Matthew Wilcox
2018-02-11 21:01         ` Matthew Wilcox
2018-02-11 21:01         ` Matthew Wilcox
2018-02-11  3:19 ` [PATCH 3/6] struct page: add field for vm_struct Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11 21:16   ` Matthew Wilcox
2018-02-11 21:16     ` Matthew Wilcox
2018-02-11 21:16     ` Matthew Wilcox
2018-02-12 16:24     ` Igor Stoppa
2018-02-12 16:24       ` Igor Stoppa
2018-02-12 16:24       ` Igor Stoppa
2018-02-12 16:24       ` Igor Stoppa
2018-02-20 19:53       ` Igor Stoppa
2018-02-20 19:53         ` Igor Stoppa
2018-02-20 19:53         ` Igor Stoppa
2018-02-20 19:53         ` Igor Stoppa
2018-02-20 20:54         ` Matthew Wilcox
2018-02-20 20:54           ` Matthew Wilcox
2018-02-20 20:54           ` Matthew Wilcox
2018-02-21 12:01           ` Igor Stoppa
2018-02-21 12:01             ` Igor Stoppa
2018-02-21 12:01             ` Igor Stoppa
2018-02-21 12:01             ` Igor Stoppa
2018-02-22 14:20             ` Igor Stoppa
2018-02-22 14:20               ` Igor Stoppa
2018-02-22 14:20               ` Igor Stoppa
2018-02-22 14:20               ` Igor Stoppa
2018-02-11  3:19 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11 12:37   ` Mike Rapoport
2018-02-11 12:37     ` Mike Rapoport
2018-02-11 12:37     ` Mike Rapoport
2018-02-12 11:26     ` Igor Stoppa
2018-02-12 11:26       ` Igor Stoppa
2018-02-12 11:26       ` Igor Stoppa
2018-02-12 11:26       ` Igor Stoppa
2018-02-12 11:43       ` Mike Rapoport
2018-02-12 11:43         ` Mike Rapoport
2018-02-12 11:43         ` Mike Rapoport
2018-02-12 12:53         ` Mike Rapoport
2018-02-12 12:53           ` Mike Rapoport
2018-02-12 12:53           ` Mike Rapoport
2018-02-12 13:41           ` Igor Stoppa
2018-02-12 13:41             ` Igor Stoppa
2018-02-12 13:41             ` Igor Stoppa
2018-02-12 13:41             ` Igor Stoppa
2018-02-12 15:31             ` Mike Rapoport [this message]
2018-02-12 15:31               ` Mike Rapoport
2018-02-12 15:31               ` Mike Rapoport
2018-02-12 15:41               ` Igor Stoppa
2018-02-12 15:41                 ` Igor Stoppa
2018-02-12 15:41                 ` Igor Stoppa
2018-02-12 15:41                 ` Igor Stoppa
2018-02-11  3:19 ` [PATCH 5/6] Pmalloc: self-test Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-13  2:43   ` kbuild test robot
2018-02-13  2:43     ` kbuild test robot
2018-02-13  2:43     ` kbuild test robot
2018-02-11  3:19 ` [PATCH 6/6] Documentation for Pmalloc Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11  3:19   ` Igor Stoppa
2018-02-11 21:17   ` Matthew Wilcox
2018-02-11 21:17     ` Matthew Wilcox
2018-02-11 21:17     ` Matthew Wilcox
2018-02-12 11:28     ` Igor Stoppa
2018-02-12 11:28       ` Igor Stoppa
2018-02-12 11:28       ` Igor Stoppa
2018-02-12 11:28       ` Igor Stoppa
  -- strict thread matches above, loose matches on Subject: below --
2018-02-12 16:52 [RFC PATCH v16 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-02-12 16:52 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-12 16:52   ` Igor Stoppa
2018-02-12 16:52   ` Igor Stoppa
2018-02-12 16:52   ` Igor Stoppa
2018-02-04 16:47 [RFC PATCH v14 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-02-04 16:47 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-04 16:47   ` Igor Stoppa
2018-02-04 16:47   ` Igor Stoppa
2018-02-04 16:47   ` Igor Stoppa
2018-02-04 22:06   ` Randy Dunlap
2018-02-04 22:06     ` Randy Dunlap
2018-02-04 22:06     ` Randy Dunlap
2018-02-11  1:04     ` Igor Stoppa
2018-02-11  1:04       ` Igor Stoppa
2018-02-11  1:04       ` Igor Stoppa
2018-02-11  1:04       ` Igor Stoppa
2018-02-07 10:03   ` kbuild test robot
2018-02-07 10:03     ` kbuild test robot
2018-02-07 10:03     ` kbuild test robot
2018-02-07 22:21   ` kbuild test robot
2018-02-07 22:21     ` kbuild test robot
2018-02-07 22:21     ` kbuild test robot
2018-02-03 19:42 [RFC PATCH v13 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-02-03 19:42 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-03 19:42   ` Igor Stoppa
2018-02-03 19:42   ` Igor Stoppa
2018-02-03 19:42   ` Igor Stoppa
2018-01-30 15:14 [RFC PATCH v12 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-01-30 15:14 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-01-30 15:14   ` Igor Stoppa
2018-01-30 15:14   ` Igor Stoppa
2018-01-30 15:14   ` Igor Stoppa
2018-02-02  5:41   ` kbuild test robot
2018-02-02  5:41     ` kbuild test robot
2018-02-02  5:41     ` kbuild test robot
2018-02-02  5:53   ` kbuild test robot
2018-02-02  5:53     ` kbuild test robot
2018-02-02  5:53     ` kbuild test robot
2018-01-24 17:56 [kernel-hardening] [RFC PATCH v11 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-01-24 17:56 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-01-24 17:56   ` Igor Stoppa
2018-01-24 19:10   ` [kernel-hardening] " Jann Horn
2018-01-26  5:35     ` Matthew Wilcox
2018-02-02 18:39       ` Christopher Lameter
2018-02-03 15:38         ` Igor Stoppa
2018-02-03 19:57           ` Igor Stoppa
2018-02-03 20:12             ` Boris Lukashev
2018-02-03 20:32               ` Igor Stoppa
2018-02-03 22:29                 ` Boris Lukashev
2018-02-04 15:05                   ` Igor Stoppa
2018-02-12 23:27                     ` Kees Cook
2018-02-13  0:40                       ` Laura Abbott
2018-02-13 15:20                         ` Igor Stoppa
2018-01-26 19:41   ` Igor Stoppa
2018-01-26 19:41     ` Igor Stoppa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180212153156.GF20737@rapoport-lnx \
    --to=rppt@linux.vnet.ibm.com \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=hch@infradead.org \
    --cc=igor.stoppa@huawei.com \
    --cc=jglisse@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.