Linux MM tree latest commits
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: dan.carpenter@oracle.com, ecashin@coraid.com, mm-commits@vger.kernel.org
Subject: [merged] aoe-fix-use-after-free-in-aoedev_by_aoeaddr.patch removed from -mm tree
Date: Tue, 18 Dec 2012 12:11:35 -0800	[thread overview]
Message-ID: <20121218201136.2E2FB200059@hpza10.eem.corp.google.com> (raw)


The patch titled
     Subject: aoe: fix use after free in aoedev_by_aoeaddr()
has been removed from the -mm tree.  Its filename was
     aoe-fix-use-after-free-in-aoedev_by_aoeaddr.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Dan Carpenter <dan.carpenter@oracle.com>
Subject: aoe: fix use after free in aoedev_by_aoeaddr()

We should return NULL on failure instead of returning a freed pointer.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Ed Cashin <ecashin@coraid.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 drivers/block/aoe/aoedev.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN drivers/block/aoe/aoedev.c~aoe-fix-use-after-free-in-aoedev_by_aoeaddr drivers/block/aoe/aoedev.c
--- a/drivers/block/aoe/aoedev.c~aoe-fix-use-after-free-in-aoedev_by_aoeaddr
+++ a/drivers/block/aoe/aoedev.c
@@ -461,6 +461,7 @@ aoedev_by_aoeaddr(ulong maj, int min, in
 	d->targets = kcalloc(NTARGETS, sizeof(*d->targets), GFP_ATOMIC);
 	if (!d->targets) {
 		kfree(d);
+		d = NULL;
 		goto out;
 	}
 	d->ntargets = NTARGETS;
_

Patches currently in -mm which might be from dan.carpenter@oracle.com are

origin.patch
linux-next.patch


                 reply	other threads:[~2012-12-18 20:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20121218201136.2E2FB200059@hpza10.eem.corp.google.com \
    --to=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=ecashin@coraid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.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