From: Simone Ballarin <simone.ballarin@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
"Simone Ballarin" <simone.ballarin@bugseng.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Michal Orzel" <michal.orzel@amd.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [XEN PATCH v3 0/2] xen: address violations of MISRA C Rule 17.1
Date: Thu, 28 Mar 2024 11:29:33 +0100 [thread overview]
Message-ID: <cover.1711621080.git.simone.ballarin@bugseng.com> (raw)
MISRA C Rule 20.7 states: "The features of `<stdarg.h>' shall not be used".
The Xen community wants to avoid using variadic functions except for
specific circumstances where it feels appropriate by strict code review.
Functions hypercall_create_continuation and hypercall_xlat_continuation
are internal helpers made to break long running hypercalls into multiple
calls. They take a variable number of arguments depending on the original
hypercall they are trying to continue. Add SAF deviations for the aforementioned
functions.
Add deviation for printf()-like functions.
---
Changes in v3:
- use regexes to exempt all .*printk and .*printf functions, instead
of manually listing them one by one;
- rebase: change SAF-3-safe in SAF-4-safe.
Changes in v2:
- replace "related to console output" with "printf()-like functions";
- replace "special hypercalls" with "internal helpers".
Simone Ballarin (2):
MISRA C:2012 Rule 17.1 states: The features of `<stdarg.h>' shall not
be used
MISRA C Rule 20.7 states: "The features of `<stdarg.h>' shall not be
used"
automation/eclair_analysis/ECLAIR/deviations.ecl | 13 +++++++++++++
docs/misra/deviations.rst | 5 +++++
docs/misra/safe.json | 8 ++++++++
xen/arch/arm/domain.c | 1 +
xen/arch/x86/hypercall.c | 2 ++
5 files changed, 29 insertions(+)
--
2.34.1
next reply other threads:[~2024-03-28 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 10:29 Simone Ballarin [this message]
2024-03-28 10:29 ` [XEN PATCH v3 1/2] MISRA C:2012 Rule 17.1 states: The features of `<stdarg.h>' shall not be used Simone Ballarin
2024-04-05 0:25 ` Stefano Stabellini
2024-03-28 10:29 ` [XEN PATCH v3 2/2] MISRA C Rule 20.7 states: "The features of `<stdarg.h>' shall not be used" Simone Ballarin
2024-03-28 10:31 ` Jan Beulich
2024-03-28 10:50 ` Simone Ballarin
2024-04-05 0:27 ` Stefano Stabellini
2024-04-05 6:45 ` Jan Beulich
2024-04-05 18:16 ` 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=cover.1711621080.git.simone.ballarin@bugseng.com \
--to=simone.ballarin@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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.