From: Andries Brouwer <aebr@win.tue.nl>
To: Christoph Hellwig <hch@lst.de>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fix sector_div use in scsicam.c
Date: Sun, 27 Oct 2002 20:22:28 +0100 [thread overview]
Message-ID: <20021027192228.GA28395@win.tue.nl> (raw)
In-Reply-To: <20021027173756.A16077@lst.de>
On Sun, Oct 27, 2002 at 05:37:56PM +0100, Christoph Hellwig wrote:
> On Sun, Oct 27, 2002 at 10:34:09AM -0600, James Bottomley wrote:
Hi Christoph & James,
I see you trying to get this scsicam code do something
that it should not. No 64-bit handling required or even desirable.
Any use of sector_div here is wrong.
I answered this yesterday or the day before or so, but maybe
you did not see the reply.
> --- 1.11/drivers/scsi/scsicam.c Fri Oct 25 13:31:53 2002
> +++ edited/drivers/scsi/scsicam.c Sun Oct 27 16:36:31 2002
> @@ -80,11 +80,13 @@
> if (ret || ip[0] > 255 || ip[1] > 63) {
> ip[0] = 64;
> ip[1] = 32;
> - if (sector_div(capacity, ip[0] * ip[1]) > 65534) {
> + sector_div(capacity, ip[0] * ip[1]);
> + if (capacity > 65534) {
> ip[0] = 255;
> ip[1] = 63;
> + sector_div(capacity, ip[0] * ip[1]);
> }
> - ip[2] = sector_div(capacity, ip[0] * ip[1]);
> + ip[2] = capacity;
> }
>
> return 0;
Write, e.g.,
if (ret || ip[0] > 255 || ip[1] > 63) {
ip[0] = 64;
ip[1] = 32;
if ((capacity >> 11) > 65534) {
ip[0] = 255;
ip[1] = 63;
}
if (capacity > 65535*63*255)
ip[2] = 65535;
else
ip[2] = (unsigned long)capacity / (ip[0] * ip[1]);
}
Andries
next prev parent reply other threads:[~2002-10-27 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 16:02 [PATCH] fix sector_div use in scsicam.c Christoph Hellwig
2002-10-27 16:21 ` James Bottomley
2002-10-27 16:23 ` Christoph Hellwig
2002-10-27 16:34 ` James Bottomley
2002-10-27 16:37 ` Christoph Hellwig
2002-10-27 19:22 ` Andries Brouwer [this message]
2002-10-27 20:53 ` James Bottomley
2002-10-27 22:10 ` Andries Brouwer
2002-10-28 0:05 ` James Bottomley
2002-10-28 0:50 ` Andries Brouwer
2002-10-28 1:45 ` Christoph Hellwig
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=20021027192228.GA28395@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=James.Bottomley@steeleye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.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.