From: Michael Ellerman <mpe@ellerman.id.au>
To: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] opal: Fix the overflow of message notifiers head array
Date: Wed, 11 Feb 2015 14:14:38 +1100 [thread overview]
Message-ID: <1423624478.12568.2.camel@ellerman.id.au> (raw)
In-Reply-To: <20150210171245.28320.53659.stgit@localhost.localdomain>
On Tue, 2015-02-10 at 22:44 +0530, Neelesh Gupta wrote:
You forgot to write the changelog.
> Signed-off-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
> Reviewed-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
> ---
> arch/powerpc/platforms/powernv/opal.c | 12 ++++--------
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c
> index f10b9ec..2651e22 100644
> --- a/arch/powerpc/platforms/powernv/opal.c
> +++ b/arch/powerpc/platforms/powernv/opal.c
> @@ -305,16 +305,12 @@ void opal_notifier_disable(void)
> int opal_message_notifier_register(enum OpalMessageType msg_type,
> struct notifier_block *nb)
> {
> - if (!nb) {
> - pr_warning("%s: Invalid argument (%p)\n",
> - __func__, nb);
> - return -EINVAL;
> - }
> - if (msg_type > OPAL_MSG_TYPE_MAX) {
> - pr_warning("%s: Invalid message type argument (%d)\n",
> + if (!nb || msg_type >= OPAL_MSG_TYPE_MAX) {
> + pr_warning("%s: Invalid arguments, msg_type:%d\n",
> __func__, msg_type);
> return -EINVAL;
> }
> +
> return atomic_notifier_chain_register(
> &opal_msg_notifier_head[msg_type], nb);
> }
> @@ -351,7 +347,7 @@ static void opal_handle_message(void)
> type = be32_to_cpu(msg.msg_type);
>
> /* Sanity check */
> - if (type > OPAL_MSG_TYPE_MAX) {
> + if (type >= OPAL_MSG_TYPE_MAX) {
> pr_warning("%s: Unknown message type: %u\n", __func__, type);
> return;
> }
>
prev parent reply other threads:[~2015-02-11 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 17:14 [PATCH 1/2] opal: Fix the overflow of message notifiers head array Neelesh Gupta
2015-02-10 17:15 ` [PATCH 2/2] opal: Add message notifier unregister function Neelesh Gupta
2015-02-11 3:14 ` Michael Ellerman [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=1423624478.12568.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=neelegup@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).