Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Wed, 30 Mar 2022 13:20:14 -0700
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
Message-ID: <YkS7fiItcIBH18C4@google.com>
References: <20220330175850.2030509-1-wonchung@google.com>
 <CAFivqmLqDXWDyEiYMXvkjQTif9jjqau5nE9YtpYyy=F-PybvDg@mail.gmail.com>
 <CAOvb9yimjRJiX-RD8L_BUdpSWeZ+a76do=f-1-NDXC2Q2VjQ6g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="GHrXQ45rgVODPjoz"
Content-Disposition: inline
In-Reply-To: <CAOvb9yimjRJiX-RD8L_BUdpSWeZ+a76do=f-1-NDXC2Q2VjQ6g@mail.gmail.com>
Precedence: bulk


--GHrXQ45rgVODPjoz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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> wro=
te:
> >
> > 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 branc=
hes.
> > Also, please use my chromium.org account (pmalani@chromium.org) for ups=
tream communications.
> >
> > Thanks!
>=20
> Hi Prashant,
>=20
> 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.
>=20

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.
>=20
> Thanks,
> Won

Thanks,
Benson

--=20
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

--GHrXQ45rgVODPjoz
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQCtZK6p/AktxXfkOlzbaomhzOwwgUCYkS7fQAKCRBzbaomhzOw
wvMgAP9l7ZFw1Hj6Mlthn3iGa6RqN0HG1Ll8Mgs65Al5eaJmKQEA59+1Rd34bTsG
PJ8CK8Vgy69vW+jTzLGY9iIKhVIP5QM=
=p7Li
-----END PGP SIGNATURE-----

--GHrXQ45rgVODPjoz--