All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "jslaby@suse.cz" <jslaby@suse.cz>
Cc: "geert@linux-m68k.org" <geert@linux-m68k.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"dmarkh@cfl.rr.com" <dmarkh@cfl.rr.com>,
	"hare@suse.de" <hare@suse.de>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "sd: Disable support for 256 byte/sector disks" has been added to the 4.0-stable tree
Date: Wed, 03 Jun 2015 06:54:29 -0700	[thread overview]
Message-ID: <1433339669.2251.61.camel@HansenPartnership.com> (raw)
In-Reply-To: <1433338620.2251.57.camel@Odin.com>

On Wed, 2015-06-03 at 13:37 +0000, James Bottomley wrote:
> On Wed, 2015-06-03 at 11:29 +0200, Jiri Slaby wrote:
> > On 06/03/2015, 08:35 AM, gregkh@linuxfoundation.org wrote:
> > > From 74856fbf441929918c49ff262ace9835048e4e6a Mon Sep 17 00:00:00 2001
> > > From: Mark Hounschell <dmarkh@cfl.rr.com>
> > > Date: Wed, 13 May 2015 10:49:09 +0200
> > > Subject: sd: Disable support for 256 byte/sector disks
> > > 
> > > From: Mark Hounschell <dmarkh@cfl.rr.com>
> > > 
> > > commit 74856fbf441929918c49ff262ace9835048e4e6a upstream.
> > > 
> > > 256 bytes per sector support has been broken since 2.6.X,
> > > and no-one stepped up to fix this.
> > > So disable support for it.
> > > 
> > > Signed-off-by: Mark Hounschell <dmarkh@cfl.rr.com>
> > > Signed-off-by: Hannes Reinecke <hare@suse.de>
> > > Signed-off-by: James Bottomley <JBottomley@Odin.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > 
> > > ---
> > >  drivers/scsi/sd.c |   19 +++++--------------
> > >  1 file changed, 5 insertions(+), 14 deletions(-)
> > > 
> > > --- a/drivers/scsi/sd.c
> > > +++ b/drivers/scsi/sd.c
> > > @@ -1624,6 +1624,7 @@ static unsigned int sd_completed_bytes(s
> > >  {
> > >  	u64 start_lba = blk_rq_pos(scmd->request);
> > >  	u64 end_lba = blk_rq_pos(scmd->request) + (scsi_bufflen(scmd) / 512);
> > > +	u64 factor = scmd->device->sector_size / 512;
> > >  	u64 bad_lba;
> > >  	int info_valid;
> > >  	/*
> > > @@ -1645,16 +1646,9 @@ static unsigned int sd_completed_bytes(s
> > >  	if (scsi_bufflen(scmd) <= scmd->device->sector_size)
> > >  		return 0;
> > >  
> > > -	if (scmd->device->sector_size < 512) {
> > > -		/* only legitimate sector_size here is 256 */
> > > -		start_lba <<= 1;
> > > -		end_lba <<= 1;
> > > -	} else {
> > > -		/* be careful ... don't want any overflows */
> > > -		unsigned int factor = scmd->device->sector_size / 512;
> > > -		do_div(start_lba, factor);
> > > -		do_div(end_lba, factor);
> > > -	}
> > 
> > Hmm, you do 'unsigned int' -> 'u64' switch of factor type here. But this
> > commit:
> > commit ef80d1e18b014af08741cf688e3fdda1fb71363f
> > Author: Geert Uytterhoeven <geert@linux-m68k.org>
> > Date:   Mon Nov 4 10:21:05 2013 +0100
> > 
> >     [SCSI] sd: Do not call do_div() with a 64-bit divisor
> > 
> > did the switch in the opposite direction deliberately.
> > 
> > So why did you do the change, given sector_size is uint?
> 
> Primarily because no-one spotted the reversal and none of the static
> checkers warns about it.
> 
> This is the trivial fix, but we should do something about the checkers.

Actually, I think there's no problem: all the architectures now have the
correct conversion of the base argument.

Author: Andreas Schwab <schwab@linux-m68k.org>
Date:   Fri Aug 9 15:14:08 2013 +0200

    m68k: Truncate base in do_div()

Fixed this in m68k, which was the last one, so it looks like there's no
issue and ef80d1e18b014af08741cf688e3fdda1fb71363f was pointless.

James


  reply	other threads:[~2015-06-03 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  6:35 Patch "sd: Disable support for 256 byte/sector disks" has been added to the 4.0-stable tree gregkh
2015-06-03  9:29 ` Jiri Slaby
2015-06-03 13:37   ` James Bottomley
2015-06-03 13:54     ` James Bottomley [this message]
2015-06-03 14:37       ` Geert Uytterhoeven

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=1433339669.2251.61.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dmarkh@cfl.rr.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.de \
    --cc=jslaby@suse.cz \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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.