From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] component: fix debugfs.
Date: Tue, 14 Jan 2020 16:09:56 +0100 [thread overview]
Message-ID: <20200114150956.GA1977145@kroah.com> (raw)
In-Reply-To: <20191218141207.23156-1-arnaud.pouliquen@st.com>
On Wed, Dec 18, 2019 at 03:12:07PM +0100, Arnaud Pouliquen wrote:
> In component_devices_show function, the data field
> of the component_match_array structure can not match with the
> device structure type. As mentioned in component_match_add_release
> description, data field type is undefined. This can result to an
> unexpected print or can generate an overflow.
> Seems no generic way to get the component name, so this patch
> prints the component device name only if registered.
>
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Good catch, someone else fixed this right before you did, so I'll queue
up that patch, thanks.
greg k-h
prev parent reply other threads:[~2020-01-14 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:12 [PATCH] component: fix debugfs Arnaud Pouliquen
2020-01-14 15:09 ` Greg Kroah-Hartman [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=20200114150956.GA1977145@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnaud.pouliquen@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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