linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jacmet@sunsite.dk, linux-usb@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ldv-project@linuxtesting.org, andrianov <andrianov@ispras.ru>
Subject: Re: [PATCH] usb/c67x00/c67x00-drv: Fix Data Race bug
Date: Fri, 28 Aug 2020 21:49:27 +0530	[thread overview]
Message-ID: <CAD=jOEYCXGrsaGsZebGR56f+JDN3fH2iy=htrpprCFHKxLk8Lg@mail.gmail.com> (raw)
In-Reply-To: <20200828074035.GB942935@kroah.com>

On Fri, Aug 28, 2020 at 1:10 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, Aug 26, 2020 at 08:14:59PM +0530, madhuparnabhowmik10@gmail.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> >
> > Currently in c67x00_drv_probe() IRQ is requested before calling
> > c67x00_probe_sie() and hence if interrupt happens the reading of certain
> > variables in the handler can race with initialization of the variables,
> > for e.g. sie->sie_num is written in c67x00_probe_sie() and read in
> >  c67x00_hcd_irq().
> > Hence, this patch calls c67x00_probe_sie() before requesting IRQ in
> > probe.
> >
> > Found by Linux Driver Verification project (linuxtesting.org).
> >
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> > ---
> >  drivers/usb/c67x00/c67x00-drv.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/usb/c67x00/c67x00-drv.c b/drivers/usb/c67x00/c67x00-drv.c
> > index 53838e7d4eef..2e816d5ca0eb 100644
> > --- a/drivers/usb/c67x00/c67x00-drv.c
> > +++ b/drivers/usb/c67x00/c67x00-drv.c
> > @@ -146,6 +146,9 @@ static int c67x00_drv_probe(struct platform_device *pdev)
> >       c67x00_ll_init(c67x00);
> >       c67x00_ll_hpi_reg_init(c67x00);
> >
> > +     for (i = 0; i < C67X00_SIES; i++)
> > +             c67x00_probe_sie(&c67x00->sie[i], c67x00, i);
> > +
> >       ret = request_irq(res2->start, c67x00_irq, 0, pdev->name, c67x00);
> >       if (ret) {
> >               dev_err(&pdev->dev, "Cannot claim IRQ\n");
> > @@ -158,9 +161,6 @@ static int c67x00_drv_probe(struct platform_device *pdev)
> >               goto reset_failed;
> >       }
> >
> > -     for (i = 0; i < C67X00_SIES; i++)
> > -             c67x00_probe_sie(&c67x00->sie[i], c67x00, i);
> > -
> >       platform_set_drvdata(pdev, c67x00);
> >
> >       return 0;
>
> Have you tested this on hardware to verify it works properly?

No, I haven't, don't think I have the relevant hardware.
It would be great if someone could test this and add a Tested-by tag.

Thanks,
Madhuparna

>
> thanks,
>
> greg k-h

      reply	other threads:[~2020-08-28 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 14:44 [PATCH] usb/c67x00/c67x00-drv: Fix Data Race bug madhuparnabhowmik10
2020-08-28  7:40 ` Greg KH
2020-08-28 16:19   ` Madhuparna Bhowmik [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='CAD=jOEYCXGrsaGsZebGR56f+JDN3fH2iy=htrpprCFHKxLk8Lg@mail.gmail.com' \
    --to=madhuparnabhowmik10@gmail.com \
    --cc=andrianov@ispras.ru \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacmet@sunsite.dk \
    --cc=ldv-project@linuxtesting.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 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).