All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simone Ballarin <simone.ballarin@bugseng.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
	Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH 02/13] automation/eclair: add text-based deviation for empty headers
Date: Wed, 30 Aug 2023 12:25:23 +0200	[thread overview]
Message-ID: <065c5b97-88b2-644b-8267-2e2f5958a9db@bugseng.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2308281500020.6458@ubuntu-linux-20-04-desktop>

On 29/08/23 00:00, Stefano Stabellini wrote:
> On Mon, 28 Aug 2023, Simone Ballarin wrote:
>> This patch adds a text-based deviation for Directive 4.10:
>> "Precautions shall be taken in order to prevent the contents of
>> a header file being included more than once"
>>
>> Headers starting with the following comment are not supposed to
>> comply with the directive:
>> "/* empty */"
>>
>> These headers should be empty, therefore they pose no risk if included
>> more than once.
>>
>> Signed-off-by: Simone Ballarin <simone.ballarin@bugseng.com>
> 
> Acked-by: Stefano Stabellini <sstabellini@kernel.org>
> 
> However I think we should also update rules.rst and/or update
> docs/misra/safe.json

I will do it in the next submission.
> 
> 
>> ---
>>   automation/eclair_analysis/ECLAIR/deviations.ecl | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/automation/eclair_analysis/ECLAIR/deviations.ecl b/automation/eclair_analysis/ECLAIR/deviations.ecl
>> index 5f068377fa..2681a4cff5 100644
>> --- a/automation/eclair_analysis/ECLAIR/deviations.ecl
>> +++ b/automation/eclair_analysis/ECLAIR/deviations.ecl
>> @@ -80,6 +80,7 @@ inline functions."
>>   
>>   -doc_begin="This header file is autogenerated or empty, therefore it poses no
>>   risk if included more than once."
>> +-config=MC3R1.D4.10,reports+={safe, "first_area(text(^/\\* empty \\*/$, begin-1))"}
>>   -file_tag+={empty_header, "^xen/arch/arm/efi/runtime\\.h$"}
>>   -file_tag+={autogen_headers, "^xen/include/xen/compile\\.h$||^xen/include/generated/autoconf.h$||^xen/include/xen/hypercall-defs.h$"}
>>   -config=MC3R1.D4.10,reports+={safe, "all_area(all_loc(file(empty_header||autogen_headers)))"}
>> -- 
>> 2.34.1
>>
> 

-- 
Simone Ballarin, M.Sc.

Field Application Engineer, BUGSENG (https://bugseng.com)



  reply	other threads:[~2023-08-30 10:25 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 13:19 [XEN PATCH 00/13] address violations of MISRA C:2012 Directive 4.10 Simone Ballarin
2023-08-28 13:19 ` [XEN PATCH 01/13] misra: add deviation for headers that explicitly avoid guards Simone Ballarin
2023-08-28 21:59   ` Stefano Stabellini
2023-08-28 22:32     ` Stefano Stabellini
2023-08-30  8:47       ` Simone Ballarin
2023-08-29  6:33   ` Jan Beulich
2023-08-30  8:46     ` Simone Ballarin
2023-08-28 13:19 ` [XEN PATCH 02/13] automation/eclair: add text-based deviation for empty headers Simone Ballarin
2023-08-28 22:00   ` Stefano Stabellini
2023-08-30 10:25     ` Simone Ballarin [this message]
2023-08-29  6:35   ` Jan Beulich
2023-08-30 11:27     ` Simone Ballarin
2023-08-28 13:20 ` [XEN PATCH 03/13] xen/arm: address violations of MISRA C:2012 Directive 4.10 Simone Ballarin
2023-08-28 22:02   ` Stefano Stabellini
2023-08-28 22:10   ` Julien Grall
2023-08-30 12:53     ` Simone Ballarin
2023-08-30 13:01       ` Jan Beulich
2023-08-30 13:06         ` Simone Ballarin
2023-08-28 13:20 ` [XEN PATCH 04/13] xen/x86: " Simone Ballarin
2023-08-28 22:11   ` Stefano Stabellini
2023-08-29 13:21   ` Jan Beulich
2023-08-28 13:20 ` [XEN PATCH 05/13] automation/eclair: add deviation for usercopy.c Simone Ballarin
2023-08-28 22:27   ` Stefano Stabellini
2023-08-29  6:41     ` Jan Beulich
2023-08-30 14:47     ` Simone Ballarin
2023-08-31  1:56       ` Stefano Stabellini
2023-08-31  9:24         ` Jan Beulich
2023-09-04 12:43     ` Luca Fancellu
2023-08-28 13:20 ` [XEN PATCH 06/13] x86/EFI: address violations of MISRA C:2012 Directive 4.10 Simone Ballarin
2023-08-28 22:28   ` Stefano Stabellini
2023-08-29 13:27   ` Jan Beulich
2023-08-30 15:16     ` Simone Ballarin
2023-08-28 13:20 ` [XEN PATCH 07/13] x86/asm: " Simone Ballarin
2023-08-28 22:30   ` Stefano Stabellini
2023-08-30 15:23     ` Simone Ballarin
2023-08-29  6:44   ` Jan Beulich
2023-08-28 13:20 ` [XEN PATCH 08/13] x86/mm: " Simone Ballarin
2023-08-28 22:35   ` Stefano Stabellini
2023-08-28 13:20 ` [XEN PATCH 09/13] xen/common: " Simone Ballarin
2023-08-28 22:41   ` Stefano Stabellini
2023-08-29  6:50   ` Jan Beulich
2023-08-31 10:08     ` Simone Ballarin
2023-08-31 11:10       ` Jan Beulich
2023-08-31 12:54         ` Simone Ballarin
2023-08-31 13:05           ` Jan Beulich
2023-08-31 13:30             ` Simone Ballarin
2023-09-05 22:18               ` Stefano Stabellini
2023-09-06  6:28                 ` Jan Beulich
2023-09-06  7:35                 ` Simone Ballarin
2023-08-28 13:20 ` [XEN PATCH 10/13] xen/efi: " Simone Ballarin
2023-08-28 22:42   ` Stefano Stabellini
2023-08-29  6:47     ` Jan Beulich
2023-08-28 13:20 ` [XEN PATCH 11/13] xen/sched: " Simone Ballarin
2023-08-28 22:43   ` Stefano Stabellini
2023-08-30 14:54   ` George Dunlap
2023-08-28 13:20 ` [XEN PATCH 12/13] xen: " Simone Ballarin
2023-08-28 22:51   ` Stefano Stabellini
2023-08-31 12:18     ` Simone Ballarin
2023-08-31 12:25       ` Jan Beulich
2023-09-05 22:27       ` Stefano Stabellini
2023-09-06  6:32         ` Jan Beulich
2023-09-07  1:12           ` Stefano Stabellini
2023-08-29  6:54   ` Jan Beulich
2023-08-28 13:20 ` [XEN PATCH 13/13] x86/asm: " Simone Ballarin
2023-08-28 22:45   ` Stefano Stabellini

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=065c5b97-88b2-644b-8267-2e2f5958a9db@bugseng.com \
    --to=simone.ballarin@bugseng.com \
    --cc=cardoe@cardoe.com \
    --cc=consulting@bugseng.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.