From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Julien Grall <julien@xen.org>
Cc: Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
consulting@bugseng.com,
Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
roger.pau@citrix.com, George Dunlap <george.dunlap@citrix.com>,
Wei Liu <wl@xen.org>
Subject: Re: MISRA C:2012 D4.11 caution on staging
Date: Wed, 18 Oct 2023 14:52:42 +0200 [thread overview]
Message-ID: <87b5936151ace813d9dc9592ee35f86e@bugseng.com> (raw)
In-Reply-To: <c47528e7-e202-4b5b-85ae-3bb0d1d0b608@xen.org>
On 18/10/2023 14:38, Julien Grall wrote:
> Hi Nicola,
>
> On 18/10/2023 13:30, Nicola Vetrini wrote:
>> On 17/10/2023 15:28, Julien Grall wrote:
>> I tested this, and the report is prevented by the ASSERT. It's up to
>> the maintainers to
>> decide how do you want to proceed: my suggestion is deviating it,
>
> It is not clear to me what would you deviate. Can you clarify?
>
> Cheers,
The memcpy call, as in:
/* SAF-x-false-positive-eclair */
memcpy(d->handle, config->handle, sizeof(d->handle));
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-10-18 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 9:31 MISRA C:2012 D4.11 caution on staging Nicola Vetrini
2023-10-11 0:01 ` Stefano Stabellini
2023-10-13 9:23 ` Julien Grall
2023-10-11 0:15 ` Andrew Cooper
2023-10-11 7:47 ` Nicola Vetrini
2023-10-11 7:51 ` Andrew Cooper
2023-10-13 9:27 ` Julien Grall
2023-10-13 15:11 ` Nicola Vetrini
2023-10-16 18:06 ` Julien Grall
2023-10-17 6:11 ` Jan Beulich
2023-10-17 13:28 ` Julien Grall
2023-10-18 12:30 ` Nicola Vetrini
2023-10-18 12:38 ` Julien Grall
2023-10-18 12:52 ` Nicola Vetrini [this message]
2023-10-18 13:02 ` Julien Grall
2023-10-18 21:33 ` Stefano Stabellini
2023-10-23 10:34 ` Nicola Vetrini
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=87b5936151ace813d9dc9592ee35f86e@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.