From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Won Chung <wonchung@google.com>
Cc: Tomas Winkler <tomas.winkler@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 v3] misc/mei: Add NULL check to component match callback functions
Date: Thu, 31 Mar 2022 12:27:23 +0300 [thread overview]
Message-ID: <YkVz+1HkSeXcIux2@kuha.fi.intel.com> (raw)
In-Reply-To: <20220331084918.2592699-1-wonchung@google.com>
Hi Won,
On Thu, Mar 31, 2022 at 08:49:18AM +0000, Won Chung 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.
>
> Fixes: 1e8d19d9b0dfc ("mei: hdcp: bind only with i915 on the same PCH")
> Fixes: c2004ce99ed73 ("mei: pxp: export pavp client to me client bus")
> Suggested-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Suggested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Won Chung <wonchung@google.com>
> Cc: stable@vger.kernel.org
> ---
> Changes from v2:
> - Correctly add "Suggested-by" tag
> - Add "Cc: stable@vger.kernel.org"
>
> Changes from v1:
> - Add "Fixes" tag
> - Send to stable@vger.kernel.org
You are sending these really fast. Before you send the next one,
please wait for at least one day.
thanks,
--
heikki
prev parent reply other threads:[~2022-03-31 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 8:49 Won Chung
2022-03-31 9:00 ` Greg KH
2022-03-31 9:32 ` Heikki Krogerus
2022-03-31 11:38 ` Greg KH
2022-03-31 16:04 ` Benson Leung
2022-03-31 16:57 ` Greg KH
2022-03-31 9:27 ` Heikki Krogerus [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=YkVz+1HkSeXcIux2@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=bleung@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pmalani@chromium.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®