From: Rene Herman <rene.herman@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Al Viro <viro@ftp.linux.org.uk>,
Jesper Juhl <jesper.juhl@gmail.com>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike.miller@hp.com
Subject: Re: [PATCH] Re: cciss: warning: right shift count >= width of type
Date: Mon, 13 Aug 2007 01:08:23 +0200 [thread overview]
Message-ID: <46BF92E7.2060104@gmail.com> (raw)
In-Reply-To: <1186950769.3400.34.camel@localhost.localdomain>
On 08/12/2007 10:32 PM, James Bottomley wrote:
> On Sun, 2007-08-12 at 07:58 +0100, Al Viro wrote:
>> On Sun, Aug 12, 2007 at 03:21:57AM +0200, Rene Herman wrote:
>>> @@ -2609,13 +2609,13 @@ static void do_cciss_request(request_queue_t *q)
>>> } else {
>>> c->Request.CDBLen = 16;
>>> c->Request.CDB[1]= 0;
>>> - c->Request.CDB[2]= (start_blk >> 56) & 0xff; //MSB
>>> - c->Request.CDB[3]= (start_blk >> 48) & 0xff;
>>> - c->Request.CDB[4]= (start_blk >> 40) & 0xff;
>>> - c->Request.CDB[5]= (start_blk >> 32) & 0xff;
>>> - c->Request.CDB[6]= (start_blk >> 24) & 0xff;
>>> - c->Request.CDB[7]= (start_blk >> 16) & 0xff;
>>> - c->Request.CDB[8]= (start_blk >> 8) & 0xff;
>>> + c->Request.CDB[2]= ((u64)start_blk >> 56) & 0xff; //MSB
>>> + c->Request.CDB[3]= ((u64)start_blk >> 48) & 0xff;
>>> + c->Request.CDB[4]= ((u64)start_blk >> 40) & 0xff;
>>> + c->Request.CDB[5]= ((u64)start_blk >> 32) & 0xff;
>>> + c->Request.CDB[6]= ((u64)start_blk >> 24) & 0xff;
>>> + c->Request.CDB[7]= ((u64)start_blk >> 16) & 0xff;
>>> + c->Request.CDB[8]= ((u64)start_blk >> 8) & 0xff;
>> put_unaligned(cpu_to_be64(start_blk), &c->Request.CDB[2]);
>>
>> which is what's happening here anyway.
>
> Well ... this was debated a while ago ad nauseam:
>
> http://marc.info/?t=117699555300010
>
> The main objection to what you propose is that it forces the u64
> coercion even in the 32 bit start_blk case. The preferred solution as a
> result of that debate was simply to us a macro Andrew introduced:
>
> upper_32_bits()
>
> Which will silently replace zero in the non LBD case. I actually
> thought this had already been done.
I see. Will assume it's somewhere in the pipeline.
Rene.
prev parent reply other threads:[~2007-08-12 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 0:28 cciss: warning: right shift count >= width of type Jesper Juhl
2007-08-12 0:56 ` Jesper Juhl
2007-08-12 1:25 ` [PATCH] " Rene Herman
2007-08-12 1:54 ` Rene Herman
2007-08-12 1:21 ` Rene Herman
2007-08-12 6:58 ` Al Viro
2007-08-12 19:55 ` Rene Herman
2007-08-12 20:32 ` James Bottomley
2007-08-12 23:08 ` Rene Herman [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=46BF92E7.2060104@gmail.com \
--to=rene.herman@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Mike.miller@hp.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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