From: Dan Carpenter <error27@gmail.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
linux-ide@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] ata: pata_hpt3x2n: prevent potential forever loop in hpt3xn_calibrate_dpll()
Date: Tue, 14 Feb 2023 10:06:39 +0300 [thread overview]
Message-ID: <Y+sy/zldAljT5Sir@kadam> (raw)
In-Reply-To: <48330abf-31ee-d0d1-7542-6d6a2de71dfc@opensource.wdc.com>
On Tue, Feb 14, 2023 at 12:47:52PM +0900, Damien Le Moal wrote:
> On 2/1/23 23:10, Dan Carpenter wrote:
> > This code accidentally reuses "tries" as the iterator for both the inside
> > and outside loops. It means that the potentially the "tries" could be
> > reset to 0x1000 and never reach 0x5000.
> >
> > Fixes: 669a5db411d8 ("[libata] Add a bunch of PATA drivers.")
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> > ---
> > drivers/ata/pata_hpt3x2n.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/ata/pata_hpt3x2n.c b/drivers/ata/pata_hpt3x2n.c
> > index 617c95522f43..447dc287a2d4 100644
> > --- a/drivers/ata/pata_hpt3x2n.c
> > +++ b/drivers/ata/pata_hpt3x2n.c
> > @@ -380,14 +380,14 @@ static int hpt3xn_calibrate_dpll(struct pci_dev *dev)
> > {
> > u8 reg5b;
> > u32 reg5c;
> > - int tries;
> > + int tries, tries2;
> >
> > for (tries = 0; tries < 0x5000; tries++) {
> > udelay(50);
> > pci_read_config_byte(dev, 0x5b, ®5b);
> > if (reg5b & 0x80) {
> > /* See if it stays set */
> > - for (tries = 0; tries < 0x1000; tries++) {
> > + for (tries2 = 0; tries2 < 0x1000; tries2++) {
> > pci_read_config_byte(dev, 0x5b, ®5b);
> > /* Failed ? */
> > if ((reg5b & 0x80) == 0)
>
> I am assuming this one is the same as for pata_hpt37x: a false positive ?
Yes, sorry.
regards,
dan carpenter
prev parent reply other threads:[~2023-02-14 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:10 [PATCH] ata: pata_hpt3x2n: prevent potential forever loop in hpt3xn_calibrate_dpll() Dan Carpenter
2023-02-01 15:02 ` Sergey Shtylyov
2023-02-14 3:47 ` Damien Le Moal
2023-02-14 7:06 ` Dan Carpenter [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=Y+sy/zldAljT5Sir@kadam \
--to=error27@gmail.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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).