linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rdunlap@infradead.org (Randy Dunlap)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 2/6] genalloc: selftest
Date: Sun, 11 Feb 2018 12:27:14 -0800	[thread overview]
Message-ID: <f95a064d-75e9-6ff3-2c11-4158a0ad1ca9@infradead.org> (raw)
In-Reply-To: <CAOFm3uGNVu87qYzPufu+gGbTwuhp3cjfhKuNDkcmwn3+ysKTdg@mail.gmail.com>

On 02/11/18 12:22, Philippe Ombredanne wrote:
> On Sun, Feb 11, 2018 at 4:19 AM, Igor Stoppa <igor.stoppa@huawei.com> wrote:
>> Introduce a set of macros for writing concise test cases for genalloc.
>>
>> The test cases are meant to provide regression testing, when working on
>> new functionality for genalloc.
>>
>> Primarily they are meant to confirm that the various allocation strategy
>> will continue to work as expected.
>>
>> The execution of the self testing is controlled through a Kconfig option.
>>
>> Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
> 
> <snip>
> 
>> --- /dev/null
>> +++ b/include/linux/genalloc-selftest.h
>> @@ -0,0 +1,26 @@
>> +/* SPDX-License-Identifier: GPL-2.0
> 
> nit... For a comment in .h this line should be instead its own comment
> as the first line:
>> +/* SPDX-License-Identifier: GPL-2.0 */

Why are we treating header files (.h) differently than .c files?
Either one can use the C++ "//" comment syntax.

> <snip>
> 
>> --- /dev/null
>> +++ b/lib/genalloc-selftest.c
>> @@ -0,0 +1,400 @@
>> +/* SPDX-License-Identifier: GPL-2.0
> 
> And for a comment in .c this line should use C++ style as the first line:
> 
>> +// SPDX-License-Identifier: GPL-2.0
> 
> Please check the docs for this (I know this can feel surprising but
> this has been debated at great length on list)
> 
> Thank you!
> 


-- 
~Randy
--
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

  reply	other threads:[~2018-02-11 20:27 UTC|newest]

Thread overview: 47+ 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 ` [PATCH 1/6] genalloc: track beginning of allocations Igor Stoppa
2018-02-11 12:24   ` Mike Rapoport
2018-02-12 11:17     ` Igor Stoppa
2018-02-12 11:36       ` Mike Rapoport
2018-02-13  0:43   ` kbuild test robot
2018-02-11  3:19 ` [PATCH 2/6] genalloc: selftest Igor Stoppa
2018-02-11 20:22   ` Philippe Ombredanne
2018-02-11 20:27     ` Randy Dunlap [this message]
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 21:16   ` Matthew Wilcox
2018-02-12 16:24     ` Igor Stoppa
2018-02-20 19:53       ` Igor Stoppa
2018-02-20 20:54         ` Matthew Wilcox
2018-02-21 12:01           ` Igor Stoppa
2018-02-22 14:20             ` Igor Stoppa
2018-02-11  3:19 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-11 12:37   ` Mike Rapoport
2018-02-12 11:26     ` Igor Stoppa
2018-02-12 11:43       ` Mike Rapoport
2018-02-12 12:53         ` Mike Rapoport
2018-02-12 13:41           ` Igor Stoppa
2018-02-12 15:31             ` Mike Rapoport
2018-02-12 15:41               ` Igor Stoppa
2018-02-11  3:19 ` [PATCH 5/6] Pmalloc: self-test Igor Stoppa
2018-02-13  2:43   ` kbuild test robot
2018-02-11  3:19 ` [PATCH 6/6] Documentation for Pmalloc Igor Stoppa
2018-02-11 21:17   ` Matthew Wilcox
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 2/6] genalloc: selftest Igor Stoppa
2018-02-12 23:50   ` Kees Cook
2018-02-20 16:59     ` Igor Stoppa
2018-02-21 22:28       ` Kees Cook
2018-02-22  9:14         ` Igor Stoppa
2018-02-22 18:28           ` 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 2/6] genalloc: selftest Igor Stoppa
2018-02-04 22:19   ` Randy Dunlap
2018-02-04 23:03     ` Matthew Wilcox
2018-02-05  0:14       ` Randy Dunlap
2018-02-09 14:30         ` Igor Stoppa
2018-02-10 22:59     ` Igor Stoppa
2018-02-07 20:25   ` kbuild test robot
2018-02-11  2:01     ` Igor Stoppa
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 2/6] genalloc: selftest 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 2/6] genalloc: selftest Igor Stoppa
2018-01-24 17:56 [RFC PATCH v11 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-01-24 17:56 ` [PATCH 2/6] genalloc: selftest 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=f95a064d-75e9-6ff3-2c11-4158a0ad1ca9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).