From: Benson Leung <bleung@google.com>
To: Won Chung <wonchung@google.com>
Cc: Prashant Malani <pmalani@chromium.org>,
Tomas Winkler <tomas.winkler@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc/mei: Add NULL check to component match callback functions
Date: Wed, 30 Mar 2022 13:20:14 -0700 [thread overview]
Message-ID: <YkS7fiItcIBH18C4@google.com> (raw)
In-Reply-To: <CAOvb9yimjRJiX-RD8L_BUdpSWeZ+a76do=f-1-NDXC2Q2VjQ6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
Hi Won,
On Wed, Mar 30, 2022 at 11:43:33AM -0700, Won Chung wrote:
> On Wed, Mar 30, 2022 at 11:18 AM Prashant Malani <pmalani@google.com> wrote:
> >
> > Hi Won,
> >
> > On Wed, 30 Mar 2022 at 10:58, Won Chung <wonchung@google.com> wrote:
> >>
> >> Component match callback functions need to check if expected data is
> >> passed to them. 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.
> >>
> > IMO this should have a "Fixes" tag, and be picked back to stable branches.
> > Also, please use my chromium.org account (pmalani@chromium.org) for upstream communications.
> >
> > Thanks!
>
> Hi Prashant,
>
> This currently does not fix a patch in the upstream, but is for a
> future patch of adding component_add to usb4_port. Would we need the
> "Fixes" tag for a future patch too?
I believe it is considered a fix to an original patch. Won, you should go
back through git blame of this file to see which original commit originally
added the component match callback in this and the other files.
> Thinking again, I think it might be a better idea to have this as a
> series of patches along with the patch to be sent after this one.
>
I think these are focused enough that you don't need to send them in series.
> I changed the recipient email to send this to your chromium.org
> account. Sorry for that.
>
> Thanks,
> Won
Thanks,
Benson
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-03-30 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 17:58 [PATCH] misc/mei: Add NULL check to component match callback functions Won Chung
[not found] ` <CAFivqmLqDXWDyEiYMXvkjQTif9jjqau5nE9YtpYyy=F-PybvDg@mail.gmail.com>
2022-03-30 18:43 ` Won Chung
2022-03-30 20:20 ` Benson Leung [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=YkS7fiItcIBH18C4@google.com \
--to=bleung@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pmalani@chromium.org \
--cc=tomas.winkler@intel.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