qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Marc Hartmayer <mhartmay@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-s390x <qemu-s390x@nongnu.org>,
	"Collin L. Walling" <walling@linux.ibm.com>
Subject: Re: [PATCH] pc-bios/s390-ccw: don't try to read the next block if end of chunk is reached
Date: Fri, 16 Apr 2021 14:56:21 +0200	[thread overview]
Message-ID: <cc06adc9-1431-33dd-03f5-540e240e714b@redhat.com> (raw)
In-Reply-To: <20210416074736.17409-1-mhartmay@linux.ibm.com>

On 16/04/2021 09.47, Marc Hartmayer wrote:
> Don't read the block if a null block number is reached, because this means that
> the end of chunk is reached.
> 
> Reviewed-by: Collin Walling <walling@linux.ibm.com>
> Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
> ---
>   pc-bios/s390-ccw/bootmap.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/pc-bios/s390-ccw/bootmap.c b/pc-bios/s390-ccw/bootmap.c
> index 44df7d16afca..b46997c0b7c1 100644
> --- a/pc-bios/s390-ccw/bootmap.c
> +++ b/pc-bios/s390-ccw/bootmap.c
> @@ -213,7 +213,7 @@ static int eckd_get_boot_menu_index(block_number_t s1b_block_nr)
>                   next_block_nr = eckd_block_num(&s1b->seek[i + 1].chs);
>               }
>   
> -            if (next_block_nr) {
> +            if (next_block_nr && !is_null_block_number(next_block_nr)) {
>                   read_block(next_block_nr, s2_next_blk,
>                              "Cannot read stage2 boot loader");
>               }

Commit 468184ec9024f4f7b5 was already a similar fix ... I wonder whether we 
have any more of those?

Anyway,
Acked-by: Thomas Huth <thuth@redhat.com>

and I'll queue it for my next pull request.



      reply	other threads:[~2021-04-16 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  7:47 [PATCH] pc-bios/s390-ccw: don't try to read the next block if end of chunk is reached Marc Hartmayer
2021-04-16 12:56 ` Thomas Huth [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=cc06adc9-1431-33dd-03f5-540e240e714b@redhat.com \
    --to=thuth@redhat.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=walling@linux.ibm.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).