All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: alexander.levin@verizon.com, martin.petersen@oracle.com,
	sumit.saxena@avagotech.com, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "[PATCH 062/135] megaraid: Fix possible NULL pointer deference in" has been added to the 4.4-stable tree
Date: Sat, 10 Sep 2016 10:15:05 +0200	[thread overview]
Message-ID: <20160910081505.GA15768@kroah.com> (raw)
In-Reply-To: <E2E442CB-5C49-400E-9E0E-852AADACF179@gmail.com>

On Fri, Sep 09, 2016 at 01:08:36PM -0400, Nicholas Krause wrote:
> 
> 
> On September 9, 2016 9:38:13 AM EDT, gregkh@linuxfoundation.org wrote:
> >
> >This is a note to let you know that I've just added the patch titled
> >
> >    [PATCH 062/135] megaraid: Fix possible NULL pointer deference in
> >
> >to the 4.4-stable tree which can be found at:
> >http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> >The filename of the patch is:
> >     0062-megaraid-Fix-possible-NULL-pointer-deference-in-mrai.patch
> >and it can be found in the queue-4.4 subdirectory.
> >
> >If you, or anyone else, feels it should not be added to the stable
> >tree,
> >please let <stable@vger.kernel.org> know about it.
> >
> >
> >From 301709c17bc50faa7f2c77797e454f3286d8ba39 Mon Sep 17 00:00:00 2001
> >From: Nicholas Krause <xerofoify@gmail.com>
> >Date: Tue, 5 Jan 2016 14:32:54 -0500
> >Subject: [PATCH 062/135] megaraid: Fix possible NULL pointer deference
> >in
> > mraid_mm_ioctl
> >
> >[ Upstream commit 7296f62f0322d808362b21064deb34f20799c20d ]
> >
> >This adds the needed check after the call to the function
> >mraid_mm_alloc_kioc in order to make sure that this function has not
> >returned NULL and therefore makes sure we do not deference a NULL
> >pointer if one is returned by mraid_mm_alloc_kioc.  Further more add
> >needed comments explaining that this function call can return NULL if
> >the list head is empty for the pointer passed in order to allow furture
> >users to understand this required pointer check.
> >
> >Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> >Acked-by: Sumit Saxena <sumit.saxena@avagotech.com>
> >Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
> >Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
> >Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >---
> > drivers/scsi/megaraid/megaraid_mm.c |    4 ++++
> > 1 file changed, 4 insertions(+)
> >
> >--- a/drivers/scsi/megaraid/megaraid_mm.c
> >+++ b/drivers/scsi/megaraid/megaraid_mm.c
> >@@ -179,8 +179,12 @@ mraid_mm_ioctl(struct file *filep, unsig
> > 
> > 	/*
> > 	 * The following call will block till a kioc is available
> >+	 * or return NULL if the list head is empty for the pointer
> >+	 * of type mraid_mmapt passed to mraid_mm_alloc_kioc
> > 	 */
> > 	kioc = mraid_mm_alloc_kioc(adp);
> >+	if (!kioc)
> >+		return -ENXIO;
> > 
> > 	/*
> > 	 * User sent the old mimd_t ioctl packet. Convert it to uioc_t.
> >
> >
> >Patches currently in stable-queue which might be from
> >xerofoify@gmail.com are
> >
> >queue-4.4/0062-megaraid-Fix-possible-NULL-pointer-deference-in-mrai.patch
> I do  not wish any of my work to
> touch the stable kernel tree.

Hahaha, sure, gladly deleted, too funny...

greg k-h

  parent reply	other threads:[~2016-09-10  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 13:38 Patch "[PATCH 062/135] megaraid: Fix possible NULL pointer deference in" has been added to the 4.4-stable tree gregkh
     [not found] ` <E2E442CB-5C49-400E-9E0E-852AADACF179@gmail.com>
2016-09-10  8:15   ` Greg KH [this message]
     [not found]     ` <13EEF8FE-318F-4C2D-ABDF-A92B2D3B19D4@gmail.com>
2016-09-10 15:15       ` Greg KH
     [not found]         ` <31bbff7b-a07c-6dbc-2ef1-6693f27d18a8@gmail.com>
2016-09-10 15:49           ` Greg KH
     [not found]             ` <9353EE1A-4103-4178-9D19-CDE5E96EE1CB@gmail.com>
2016-09-10 16:05               ` Greg KH
     [not found]                 ` <AF41C82E-0461-41E3-B35B-37C992517E68@gmail.com>
2016-09-11  7:22                   ` Greg KH

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=20160910081505.GA15768@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=martin.petersen@oracle.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sumit.saxena@avagotech.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.