LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "Phillip O'Donnell" <phillip.odonnell@gmail.com>, jeff@garzik.org
Cc: "Oskar Liljeblad" <oskar@osk.mine.nu>,
	jeff@garzik.org, linux-kernel@vger.kernel.org
Subject: [PATCH] libata: Avoid overflow in ata_tf_to_lba48() when tf->hba_lbal > 127
Date: Tue, 28 Oct 2008 16:52:20 -0700	[thread overview]
Message-ID: <ada4p2wmg5n.fsf_-_@cisco.com> (raw)
In-Reply-To: <7a9b5c320810281625kbf8904x9ba432ff0ca8c2f8@mail.gmail.com> (Phillip O'Donnell's message of "Wed, 29 Oct 2008 12:25:47 +1300")

In ata_tf_to_lba48(), when evaluating

	(tf->hob_lbal & 0xff) << 24

the expression is promoted to signed int (since int can hold all values
of u8).  However, if hob_lbal is 128 or more, then it is treated as a
negative signed value and sign-extended when promoted to u64 to | into
sectors, which leads to the MSB 32 bits of section getting set
incorrectly.

For example, Phillip O'Donnell <phillip.odonnell@gmail.com> reported
that a 1.5GB drive caused:

    ata3.00: HPA detected: current 2930277168, native 18446744072344861488

where 2930277168 == 0xAEA87B30 and 18446744072344861488 == 0xffffffffaea87b30
which shows the problem when hob_lbal is 0xae.

Fix this by adding a cast to u64, just as is used by for hob_lbah and
hob_lbam in the function.

Reported-by: Phillip O'Donnell <phillip.odonnell@gmail.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
---
Phillip, this should fix at least your cosmetic issue; can you test it
and report back?

Thanks,
  Roland

 drivers/ata/libata-core.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index bbb3cae..10424ff 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -1268,7 +1268,7 @@ u64 ata_tf_to_lba48(const struct ata_taskfile *tf)
 
 	sectors |= ((u64)(tf->hob_lbah & 0xff)) << 40;
 	sectors |= ((u64)(tf->hob_lbam & 0xff)) << 32;
-	sectors |= (tf->hob_lbal & 0xff) << 24;
+	sectors |= ((u64)(tf->hob_lbal & 0xff)) << 24;
 	sectors |= (tf->lbah & 0xff) << 16;
 	sectors |= (tf->lbam & 0xff) << 8;
 	sectors |= (tf->lbal & 0xff);

  reply	other threads:[~2008-10-28 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 17:01 sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard Oskar Liljeblad
2008-10-28 17:59 ` David Rees
2008-10-28 23:25 ` Phillip O'Donnell
2008-10-28 23:52   ` Roland Dreier [this message]
2008-10-29  2:04     ` [PATCH] libata: Avoid overflow in ata_tf_to_lba48() when tf->hba_lbal > 127 Phillip O'Donnell
2008-11-04 18:34       ` [PATCH] libata: Avoid overflow in ata_tf_read_block() " Roland Dreier
     [not found]         ` <7a9b5c320811041441q78920938q58ed7ab3cbe97253@mail.gmail.com>
2008-11-04 22:44           ` Phillip O'Donnell
2008-11-11  8:02         ` Jeff Garzik
2008-10-29 13:28     ` [PATCH] libata: Avoid overflow in ata_tf_to_lba48() " Phillip O'Donnell
2008-10-31  5:45     ` Jeff Garzik
     [not found] <fa.01zEaARwrup2dCOTuHTYxzuS9BI@ifi.uio.no>
     [not found] ` <fa.Dwk+NgWNu7+JRcsgOPCxSr7y5SQ@ifi.uio.no>
     [not found]   ` <fa.fIxdVik0iPc+lS+sd5ef+ZoALzQ@ifi.uio.no>
2008-10-30  0:39     ` Robert Hancock

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=ada4p2wmg5n.fsf_-_@cisco.com \
    --to=rdreier@cisco.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oskar@osk.mine.nu \
    --cc=phillip.odonnell@gmail.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).