The patch titled
Subject: memstick: use after free in msb_disk_release()
has been added to the -mm tree. Its filename is
memstick-use-after-free-in-msb_disk_release.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Subject: memstick: use after free in msb_disk_release()
The original code dereferenced "msb" after freeing it.
Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Acked-by: Maxim Levitsky <maximlevitsly@xxxxxxxxx>
Cc: Jens Axboe <axboe@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/memstick/core/ms_block.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/memstick/core/ms_block.c~memstick-use-after-free-in-msb_disk_release drivers/memstick/core/ms_block.c
--- a/drivers/memstick/core/ms_block.c~memstick-use-after-free-in-msb_disk_release
+++ a/drivers/memstick/core/ms_block.c
@@ -1983,9 +1983,9 @@ static int msb_disk_release(struct gendi
msb->usage_count--;
if (!msb->usage_count) {
- kfree(msb);
disk->private_data = NULL;
idr_remove(&msb_disk_idr, msb->disk_id);
+ kfree(msb);
put_disk(disk);
}
}
_
Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are
origin.patch
linux-next.patch
mm-compaction-cache-if-a-pageblock-was-scanned-and-no-pages-were-isolated-fix.patch
checkpatch-update-suggested-printk-conversions.patch
aoe-kernel-thread-handles-i-o-completions-for-simple-locking-fix.patch
memstick-use-after-free-in-msb_disk_release.patch
memstick-memory-leak-on-error-in-msb_ftl_scan.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
