Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Alan <gnomes@lxorguk.ukuu.org.uk>
Cc: tj@kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Fix division by zero
Date: Wed, 08 Apr 2015 16:03:23 +0200	[thread overview]
Message-ID: <2788063.ZcUqKDEcli@amdc1032> (raw)
In-Reply-To: <5105249.IaGgeTGhXs@amdc1032>

On Wednesday, April 08, 2015 03:52:58 PM Bartlomiej Zolnierkiewicz wrote:
> 
> Hi,
> 
> On Wednesday, April 08, 2015 01:51:36 PM Alan wrote:
> > (Coverity 1192289, 1192292, 1192294)
> > 
> > We have several controllers that in some cases use ata_timing_compute but do
> > not do UDMA. They pass 0 for UT, which ends up with us doing a division by
> > zero. We could pass some other bogus value in or we could make the libata
> > code do the sensible thing and treat a UT of 0 as meaning "I'm not asking
> > about UDMA".
> > 
> > This patches does the latter which is IMHO the more robust option.
> 
> Please note that we should not end up with the division by zero with
> existing host drivers.  EZ(v, unit) checks for v being zero and t->udma
> is non-zero only for XFER_UDMA_* xfer modes.  Currently none of host

A bit more detailed explanation for xfer_modes < XFER_UDMA_0:

#define ENOUGH(v, unit)		(((v)-1)/(unit)+1)
#define EZ(v, unit)		((v)?ENOUGH(v, unit):0)

		q->udma		= EZ(t->udma       * 1000, UT);

for xfer modes < XFER_UDMA_0 t->udma is always zero so EZ() will
return zero without any division.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

> drivers calls ata_timing_compute() on xfer mode >= XFER_UDMA_0 with
> the zero UT argument.  Such usage will be an error and while the old
> code explodes immediately, the new one will silently accept it (which
> could theoretically result in the wrong timing being set)..
> 
> Could you please enhance your patch with a validity code requiring
> non-zero UT when speed >= XFER_UDMA_0 is used in ata_timing_compute()?
> 
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
> 
> > Signed-off-by: Alan Cox <alan@linux.intel.com>
> > ---
> >  0 files changed
> > 
> > diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> > index f6cb1f1..6b1bd36 100644
> > --- a/drivers/ata/libata-core.c
> > +++ b/drivers/ata/libata-core.c
> > @@ -2966,7 +2966,8 @@ static void ata_timing_quantize(const struct ata_timing *t, struct ata_timing *q
> >  	q->recover	= EZ(t->recover    * 1000,  T);
> >  	q->dmack_hold	= EZ(t->dmack_hold * 1000,  T);
> >  	q->cycle	= EZ(t->cycle      * 1000,  T);
> > -	q->udma		= EZ(t->udma       * 1000, UT);
> > +	if (UT)
> > +		q->udma		= EZ(t->udma       * 1000, UT);
> >  }
> >  
> >  void ata_timing_merge(const struct ata_timing *a, const struct ata_timing *b,


  reply	other threads:[~2015-04-08 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 12:51 [PATCH] libata: Fix division by zero Alan
2015-04-08 13:52 ` Bartlomiej Zolnierkiewicz
2015-04-08 14:03   ` Bartlomiej Zolnierkiewicz [this message]
2015-04-08 15:04   ` One Thousand Gnomes

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=2788063.ZcUqKDEcli@amdc1032 \
    --to=b.zolnierkie@samsung.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox