From: Jan Beulich <jbeulich@suse.com>
To: victorm.lira@amd.com
Cc: "Nicola Vetrini" <nicola.vetrini@bugseng.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Federico Serafini" <federico.serafini@bugseng.com>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/3] xen/keyhandler: add missing noreturn attribute
Date: Tue, 10 Jun 2025 10:35:47 +0200 [thread overview]
Message-ID: <e2575351-851c-4d10-a1ea-cd63f086b42e@suse.com> (raw)
In-Reply-To: <20250606212712.1901838-1-victorm.lira@amd.com>
On 06.06.2025 23:27, victorm.lira@amd.com wrote:
> From: Nicola Vetrini <nicola.vetrini@bugseng.com>
>
> Function `reboot_machine' does not return, but lacks the `noreturn'
> attribute.
>
> Functions that never return should be declared with a `noreturn'
> attribute.
>
> The lack of `noreturn' causes a violation of MISRA C Rule 17.11 (not
> currently accepted in Xen), and also Rule 2.1: "A project shall not
> contain unreachable code". Depending on the compiler used and the
> compiler optimization used, the lack of `noreturn' might lead to the
> presence of unreachable code.
I continue to be unhappy about this: I still fail to see how this
"might" could materialize in the specific case here. My earlier
request for commit message improvement was specifically about making
the description match the particular case, not to add further general
wording. That said, if others feel like ack-ing this in this form, so
be it.
Jan
next prev parent reply other threads:[~2025-06-10 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 21:27 [PATCH v2 1/3] xen/keyhandler: add missing noreturn attribute victorm.lira
2025-06-06 21:27 ` [PATCH v2 2/3] xen/arm: add missing noreturn attributes victorm.lira
2025-06-06 21:27 ` [PATCH v2 3/3] xen/x86: " victorm.lira
2025-06-18 0:48 ` Stefano Stabellini
2025-06-18 15:18 ` Roger Pau Monné
2025-06-18 16:16 ` Nicola Vetrini
2025-06-18 17:25 ` Roger Pau Monné
2025-06-20 6:16 ` Jan Beulich
2025-06-18 0:45 ` [PATCH v2 2/3] xen/arm: " Stefano Stabellini
2025-06-10 8:35 ` Jan Beulich [this message]
2025-06-18 0:41 ` [PATCH v2 1/3] xen/keyhandler: add missing noreturn attribute 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=e2575351-851c-4d10-a1ea-cd63f086b42e@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=federico.serafini@bugseng.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=victorm.lira@amd.com \
--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.