From: Samuel Thibault <samuel.thibault@gnu.org>
To: qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>
Cc: damien@zamaudio.com, qemu-block@nongnu.org
Subject: Re: [PATCH] ide: Cap LBA28 capacity announcement to 2^28-1
Date: Wed, 6 Oct 2021 01:57:13 +0200 [thread overview]
Message-ID: <20211005235713.iodzsdcfazo6gtme@begin> (raw)
In-Reply-To: <20210824104344.3878849-1-samuel.thibault@ens-lyon.org>
Ping?
Samuel Thibault, le mar. 24 août 2021 12:43:44 +0200, a ecrit:
> The LBA28 capacity (at offsets 60/61 of identification) is supposed to
> express the maximum size supported by LBA28 commands. If the device is
> larger than this, we have to cap it to 2^28-1.
>
> At least NetBSD happens to be using this value to determine whether to use
> LBA28 or LBA48 for its commands, using LBA28 for sectors that don't need
> LBA48. This commit thus fixes NetBSD access to disks larger than 128GiB.
>
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> hw/ide/core.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ide/core.c b/hw/ide/core.c
> index fd69ca3167..e28f8aad61 100644
> --- a/hw/ide/core.c
> +++ b/hw/ide/core.c
> @@ -98,8 +98,12 @@ static void put_le16(uint16_t *p, unsigned int v)
> static void ide_identify_size(IDEState *s)
> {
> uint16_t *p = (uint16_t *)s->identify_data;
> - put_le16(p + 60, s->nb_sectors);
> - put_le16(p + 61, s->nb_sectors >> 16);
> + int64_t nb_sectors_lba28 = s->nb_sectors;
> + if (nb_sectors_lba28 >= 1 << 28) {
> + nb_sectors_lba28 = (1 << 28) - 1;
> + }
> + put_le16(p + 60, nb_sectors_lba28);
> + put_le16(p + 61, nb_sectors_lba28 >> 16);
> put_le16(p + 100, s->nb_sectors);
> put_le16(p + 101, s->nb_sectors >> 16);
> put_le16(p + 102, s->nb_sectors >> 32);
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-10-06 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:43 [PATCH] ide: Cap LBA28 capacity announcement to 2^28-1 Samuel Thibault
2021-09-05 7:30 ` Samuel Thibault
2021-10-05 23:57 ` Samuel Thibault [this message]
2021-10-20 8:57 ` Kevin Wolf
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=20211005235713.iodzsdcfazo6gtme@begin \
--to=samuel.thibault@gnu.org \
--cc=damien@zamaudio.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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).