From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Nicholas Krause <xerofoify@gmail.com>, jejb@linux.vnet.ibm.com
Cc: martin.petersen@oracle.co, tj@kernel.org,
James.Bottomley@HansenPartnership.com, hare@suse.de,
jthumshirn@suse.de, Wilfried.Weissmann@gmx.a, davispuh@gmail.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify
Date: Sat, 02 Jul 2016 19:16:40 +0100 [thread overview]
Message-ID: <57780508.3030200@osg.samsung.com> (raw)
In-Reply-To: <1467478843-16315-1-git-send-email-xerofoify@gmail.com>
On 02/07/16 18:00, Nicholas Krause wrote:
> This adds properly checking after the call to mvs_find_dev_mvi
> due to this function being able to return a NULL pointer and
> if this does arise we will deference it in mvs_alloc_dev due
> to this function never checking if a NULL pointer is given as
> it's input argument. Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> v3 - Make logic simpler on error path by returning -1 directly
> if mvs_find_dev_mvi returns NULL.
> v2 - Fix NULL pointer deferenece in error path by calling
> spin_unlock_irqrestore on the now NULL pointer, as returned
>
>
> drivers/scsi/mvsas/mv_sas.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/scsi/mvsas/mv_sas.c b/drivers/scsi/mvsas/mv_sas.c
> index 5b9fcff..dffab01 100644
> --- a/drivers/scsi/mvsas/mv_sas.c
> +++ b/drivers/scsi/mvsas/mv_sas.c
> @@ -1194,6 +1194,8 @@ int mvs_dev_found_notify(struct domain_device *dev, int lock)
> struct mvs_device *mvi_device;
>
> mvi = mvs_find_dev_mvi(dev);
> + if (!mvi)
> + return -1;
>
> if (lock)
> spin_lock_irqsave(&mvi->lock, flags);
>
This looks better :)
Checking the value of mvi makes sense if mvs_find_dev_mvi() can return NULL.
Reviewed-by: Luis de Bethencourt <luisbg@osg.samsung.com>
Thanks,
Luis
next parent reply other threads:[~2016-07-02 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1467478843-16315-1-git-send-email-xerofoify@gmail.com>
2016-07-02 18:16 ` Luis de Bethencourt [this message]
2016-07-02 19:05 ` [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify James Bottomley
2016-07-03 13:54 ` Luis de Bethencourt
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=57780508.3030200@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Wilfried.Weissmann@gmx.a \
--cc=davispuh@gmail.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.co \
--cc=tj@kernel.org \
--cc=xerofoify@gmail.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