From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com, jbeulich@suse.com,
andrew.cooper3@citrix.com, roger.pau@citrix.com,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>
Subject: Re: [XEN PATCH][for-4.19] domain: add ASSERT to help static analysis tools
Date: Fri, 03 Nov 2023 19:08:55 +0100 [thread overview]
Message-ID: <3e58166f7dcfb3fd3bd15614096b27ce@bugseng.com> (raw)
In-Reply-To: <3f163bb58993410183229e72eb1f227057f9b1c7.1699034273.git.nicola.vetrini@bugseng.com>
On 2023-11-03 18:58, Nicola Vetrini wrote:
> Static analysis tools may detect a possible null
> pointer dereference at line 760 (the memcpy call)
> of xen/common/domain.c. This ASSERT helps them in
> detecting that such a condition is not possible
> and also provides a basic sanity check.
>
Suggested-by: Julien Grall <julien@xen.org>
> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
This should have been present as well, I forgot to add it.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-11-03 18:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:58 [XEN PATCH][for-4.19] domain: add ASSERT to help static analysis tools Nicola Vetrini
2023-11-03 18:08 ` Nicola Vetrini [this message]
2023-11-07 4:18 ` Stefano Stabellini
2023-11-08 8:24 ` Jan Beulich
2023-11-08 11:03 ` Nicola Vetrini
2023-11-08 11:19 ` Jan Beulich
2023-11-08 13:28 ` Nicola Vetrini
2023-11-09 7:44 ` Jan Beulich
2023-11-08 13:33 ` Julien Grall
2023-11-09 7:42 ` Jan Beulich
2023-11-09 9:10 ` Julien Grall
2023-11-10 0:29 ` Stefano Stabellini
2023-11-10 9:06 ` Julien Grall
2023-11-10 16:30 ` Nicola Vetrini
2023-11-11 1:13 ` Stefano Stabellini
2023-11-14 16:05 ` Nicola Vetrini
2023-11-08 13:37 ` Andrew Cooper
2023-11-08 13:45 ` Nicola Vetrini
2023-11-10 16:56 ` Andrew Cooper
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=3e58166f7dcfb3fd3bd15614096b27ce@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.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=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/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.