From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-s390x@nongnu.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] pc-bios/s390-ccw: Use reset_psw pointer instead of hard-coded null pointer
Date: Mon, 26 Apr 2021 14:33:36 +0200 [thread overview]
Message-ID: <0dcba8f7-6203-84b0-98fd-dc9e85cb7f05@linux.ibm.com> (raw)
In-Reply-To: <20210423142440.582188-1-thuth@redhat.com>
On 4/23/21 4:24 PM, Thomas Huth wrote:
> When compiling the s390-ccw bios with clang, it emits a warning like this:
>
> pc-bios/s390-ccw/jump2ipl.c:86:9: warning: indirection of non-volatile null
> pointer will be deleted, not trap [-Wnull-dereference]
> if (*((uint64_t *)0) & RESET_PSW_MASK) {
> ^~~~~~~~~~~~~~~~
> pc-bios/s390-ccw/jump2ipl.c:86:9: note: consider using __builtin_trap() or
> qualifying pointer with 'volatile'
>
> We could add a "volatile" here to shut it up, but on the other hand,
> we also have a pointer variable called "reset_psw" in this file already
> that points to the PSW at address 0, so we can simply use that pointer
> variable instead.
LGTM, I'm just wondering why I didn't clean that up when I last changed
the file.
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Extend comment as suggested by Cornelia
>
> pc-bios/s390-ccw/jump2ipl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/pc-bios/s390-ccw/jump2ipl.c b/pc-bios/s390-ccw/jump2ipl.c
> index b9c70d64a5..73e4367e09 100644
> --- a/pc-bios/s390-ccw/jump2ipl.c
> +++ b/pc-bios/s390-ccw/jump2ipl.c
> @@ -82,8 +82,8 @@ void jump_to_low_kernel(void)
> jump_to_IPL_code(KERN_IMAGE_START);
> }
>
> - /* Trying to get PSW at zero address */
> - if (*((uint64_t *)0) & RESET_PSW_MASK) {
> + /* Trying to get PSW at zero address (pointed to by reset_psw) */
> + if (*reset_psw & RESET_PSW_MASK) {
> /*
> * Surely nobody will try running directly from lowcore, so
> * let's use 0 as an indication that we want to load the reset
>
prev parent reply other threads:[~2021-04-26 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 14:24 [PATCH v2] pc-bios/s390-ccw: Use reset_psw pointer instead of hard-coded null pointer Thomas Huth
2021-04-23 14:33 ` Cornelia Huck
2021-04-26 12:33 ` Janosch Frank [this message]
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=0dcba8f7-6203-84b0-98fd-dc9e85cb7f05@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).