From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Neelesh Gupta <neelegup@linux.vnet.ibm.com>,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
benh@kernel.crashing.org
Subject: Re: [PATCH v2 1/2] opal: Fix the overflow of message notifiers head array
Date: Wed, 11 Feb 2015 16:23:56 +0530 [thread overview]
Message-ID: <54DB34C4.4080306@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150211062616.3279.71632.stgit@localhost.localdomain>
On 02/11/2015 11:57 AM, Neelesh Gupta wrote:
> Fixes the condition check of incoming message type which can
> otherwise shoot beyond the message notifiers head array.
>
> Signed-off-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
> Reviewed-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Reviewed-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
prev parent reply other threads:[~2015-02-11 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 6:27 [PATCH v2 1/2] opal: Fix the overflow of message notifiers head array Neelesh Gupta
2015-02-11 6:27 ` [PATCH 2/2] opal: Add message notifier unregister function Neelesh Gupta
2015-02-11 10:57 ` Anshuman Khandual
2015-02-12 11:10 ` Neelesh Gupta
2015-02-11 10:53 ` Anshuman Khandual [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=54DB34C4.4080306@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).