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 13:43:11 +0200	[thread overview]
Message-ID: <20180212114310.GD20737@rapoport-lnx> (raw)
In-Reply-To: <e7ea02b4-3d43-9543-3d14-61c27e155042@huawei.com>

On Mon, Feb 12, 2018 at 01:26:28PM +0200, Igor Stoppa wrote:
> On 11/02/18 14:37, Mike Rapoport wrote:
> > On Sun, Feb 11, 2018 at 05:19:18AM +0200, Igor Stoppa wrote:
> 
> >> + * Return: 0 if the object does not belong to pmalloc, 1 if it belongs to
> >> + * pmalloc, -1 if it partially overlaps pmalloc meory, but incorectly.
> > 
> > typo:                                            ^ memory
> 
> thanks :-(
> 
> [...]
> 
> >> +/**
> >> + * When the sysfs is ready to receive registrations, connect all the
> >> + * pools previously created. Also enable further pools to be connected
> >> + * right away.
> >> + */
> > 
> > This does not seem as kernel-doc comment. Please either remove the second *
> > from the opening comment mark or reformat the comment.
> 
> For this too, I thought I had caught them all, but I was wrong ...
> 
> I didn't find any mention of automated checking for comments.
> Is there such tool?

I don't know if there is a tool. I couldn't find anything in scripts, maybe
somebody have such tool out of tree.

For now, I've added mm-api.rst that includes all mm .c files and run 'make
htmldocs' which spits plenty of warnings and errors.

> --
> thanks, igor
> 

-- 
Sincerely yours,
Mike.

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 13:43:11 +0200	[thread overview]
Message-ID: <20180212114310.GD20737@rapoport-lnx> (raw)
In-Reply-To: <e7ea02b4-3d43-9543-3d14-61c27e155042@huawei.com>

On Mon, Feb 12, 2018 at 01:26:28PM +0200, Igor Stoppa wrote:
> On 11/02/18 14:37, Mike Rapoport wrote:
> > On Sun, Feb 11, 2018 at 05:19:18AM +0200, Igor Stoppa wrote:
> 
> >> + * Return: 0 if the object does not belong to pmalloc, 1 if it belongs to
> >> + * pmalloc, -1 if it partially overlaps pmalloc meory, but incorectly.
> > 
> > typo:                                            ^ memory
> 
> thanks :-(
> 
> [...]
> 
> >> +/**
> >> + * When the sysfs is ready to receive registrations, connect all the
> >> + * pools previously created. Also enable further pools to be connected
> >> + * right away.
> >> + */
> > 
> > This does not seem as kernel-doc comment. Please either remove the second *
> > from the opening comment mark or reformat the comment.
> 
> For this too, I thought I had caught them all, but I was wrong ...
> 
> I didn't find any mention of automated checking for comments.
> Is there such tool?

I don't know if there is a tool. I couldn't find anything in scripts, maybe
somebody have such tool out of tree.

For now, I've added mm-api.rst that includes all mm .c files and run 'make
htmldocs' which spits plenty of warnings and errors.

> --
> thanks, igor
> 

-- 
Sincerely yours,
Mike.

--
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 13:43:11 +0200	[thread overview]
Message-ID: <20180212114310.GD20737@rapoport-lnx> (raw)
In-Reply-To: <e7ea02b4-3d43-9543-3d14-61c27e155042@huawei.com>

On Mon, Feb 12, 2018 at 01:26:28PM +0200, Igor Stoppa wrote:
> On 11/02/18 14:37, Mike Rapoport wrote:
> > On Sun, Feb 11, 2018 at 05:19:18AM +0200, Igor Stoppa wrote:
> 
> >> + * Return: 0 if the object does not belong to pmalloc, 1 if it belongs to
> >> + * pmalloc, -1 if it partially overlaps pmalloc meory, but incorectly.
> > 
> > typo:                                            ^ memory
> 
> thanks :-(
> 
> [...]
> 
> >> +/**
> >> + * When the sysfs is ready to receive registrations, connect all the
> >> + * pools previously created. Also enable further pools to be connected
> >> + * right away.
> >> + */
> > 
> > This does not seem as kernel-doc comment. Please either remove the second *
> > from the opening comment mark or reformat the comment.
> 
> For this too, I thought I had caught them all, but I was wrong ...
> 
> I didn't find any mention of automated checking for comments.
> Is there such tool?

I don't know if there is a tool. I couldn't find anything in scripts, maybe
somebody have such tool out of tree.

For now, I've added mm-api.rst that includes all mm .c files and run 'make
htmldocs' which spits plenty of warnings and errors.

> --
> thanks, igor
> 

-- 
Sincerely yours,
Mike.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2018-02-12 11:43 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 [this message]
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
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=20180212114310.GD20737@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.