From: Takashi Iwai <tiwai@suse.de>
To: Won Chung <wonchung@google.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Benson Leung <bleung@chromium.org>,
Prashant Malani <pmalani@chromium.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] sound/hda: Add NULL check to component match callback function
Date: Thu, 31 Mar 2022 11:12:55 +0200 [thread overview]
Message-ID: <s5hr16ieb8o.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAOvb9yiO_n48JPZ3f0+y-fQ_YoOmuWF5c692Jt5_SKbxdA4yAw@mail.gmail.com>
On Thu, 31 Mar 2022 10:38:34 +0200,
Won Chung wrote:
>
> On Thu, Mar 31, 2022 at 12:27 AM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > On Wed, 30 Mar 2022 23:19:13 +0200,
> > Won Chung wrote:
> > >
> > > Component match callback function needs to check if expected data is
> > > passed to it. Without this check, it can cause a NULL pointer
> > > dereference when another driver registers a component before i915
> > > drivers have their component master fully bind.
> > >
> > > Fixes: 7b882fe3e3e8b ("ALSA: hda - handle multiple i915 device instances")
> > > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > > Signed-off-by: Won Chung <wonchung@google.com>
> > > ---
> > > - Add "Fixes" tag
> > > - Send to stable@vger.kernel.org
> >
> > You rather need to add "Cc: stable@vger.kernel.org" line to the patch
> > itself (around sign-off block), not actually Cc'ing the mail.
> > I edited manually, but please do it so at the next time.
> >
> > Although I applied the patch as-is now, I wonder...
> >
> >
> > > - if (!strcmp(dev->driver->name, "i915") &&
> > > + if (dev->driver && !strcmp(dev->driver->name, "i915") &&
> >
> > Can NULL dev->driver be really seen? I thought the components are
> > added by the drivers, hence they ought to have the driver field set.
> > But there can be corner cases I overlooked.
> >
> >
> > thanks,
> >
> > Takashi
>
> Hi Takashi,
>
> When I try using component_add in a different driver (usb4 in my
> case), I think dev->driver here is NULL because the i915 drivers do
> not have their component master fully bound when this new component is
> registered. When I test it, it seems to be causing a crash.
Hm, from where component_add*() is called? Basically dev->driver must
be already set before the corresponding driver gets bound at
__driver_probe_deviec(). So, if the device is added to component from
the corresponding driver's probe, dev->driver must be non-NULL.
> Would it be okay for me to resend a new patch with the flags
> corrected? I have mistakenly added Heikki and Mika as "Signed-off-by"
> instead of "Suggested-by". I am sorry for that.
Ah that's bad. I'll reset the branch, then. Please resubmit
properly.
thanks,
Takashi
next prev parent reply other threads:[~2022-03-31 9:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 21:19 [PATCH v2] sound/hda: Add NULL check to component match callback function Won Chung
2022-03-31 7:27 ` Takashi Iwai
2022-03-31 8:38 ` Won Chung
2022-03-31 9:12 ` Takashi Iwai [this message]
2022-03-31 9:25 ` Heikki Krogerus
2022-03-31 9:28 ` Takashi Iwai
2022-03-31 9:34 ` Heikki Krogerus
2022-03-31 9:45 ` Takashi Iwai
2022-03-31 13:29 ` Takashi Iwai
2022-03-31 14:19 ` Takashi Iwai
2022-03-31 15:33 ` Benson Leung
2022-03-31 15:37 ` Takashi Iwai
2022-03-31 16:10 ` Mika Westerberg
2022-03-31 16:38 ` Greg KH
2022-03-31 16:58 ` Won Chung
2022-03-31 17:18 ` Greg KH
2022-03-31 17:33 ` Benson Leung
2022-03-31 17:46 ` Greg KH
2022-04-01 7:02 ` Heikki Krogerus
2022-03-31 11:39 ` Greg KH
2022-03-31 12:52 ` Heikki Krogerus
2022-03-31 12:56 ` Greg KH
2022-03-31 13:15 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2022-03-30 20:55 Won Chung
2022-03-30 21:15 ` Won Chung
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=s5hr16ieb8o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bleung@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=perex@perex.cz \
--cc=pmalani@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=wonchung@google.com \
/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