All of lore.kernel.org
 help / color / mirror / Atom feed
* [2.4.19] [2.4.20-pre6] loop.c memory allocation & freeing problem
@ 2002-09-12 20:28 Yann E. MORIN
  0 siblings, 0 replies; only message in thread
From: Yann E. MORIN @ 2002-09-12 20:28 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

Hi All!

I think I've spotted a bug in the initialisation procedure in the loop driver,
@line 1027-1060, when there is allocation failure:

----BEGIN CODE----
        loop_dev = kmalloc(max_loop * sizeof(struct loop_device), GFP_KERNEL);
        if (!loop_dev)
                return -ENOMEM;

        loop_sizes = kmalloc(max_loop * sizeof(int), GFP_KERNEL);
        if (!loop_sizes)
                goto out_sizes;

        loop_blksizes = kmalloc(max_loop * sizeof(int), GFP_KERNEL);
        if (!loop_blksizes)
                goto out_blksizes;

[...SNIP...]

out_sizes:
        kfree(loop_dev);
out_blksizes:
        kfree(loop_sizes);
----END CODE----

Two problems arise there:
1) Should allocation of loop_sizes fail, we'll try to free loop_sizes that
   was NOT allocated (no problem because kfree does not free a NULL pointer).
   But not very clean...

2) Should allocation of loop_blksizes fail, loop_dev will NOT be freed.
   That one looks more problematic.

Am I wrong? Have I missed something? Anyway it's been there for ages, I
suppose.

Patch is very straigthforward, and is attached : swap the last 2 pairs of
lines, so that out_blksizes is before out_sizes, and kfree(loop_sizes is
before kfree(loop_dev).

Please CC: answers and comments as I'm no longer subscribed.

Cheers,
Yann.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
|  0 662 376 056  | Software  Designer | \ / CAMPAIGN     |  ___               |
| --==< °_° >==-- °---.----------------:  X  AGAINST      |  \e/  There is no  |
| web: ymorin.free.fr | SETI@home  433 | / \ HTML MAIL    |   v   conspiracy.  |
°---------------------°----------------°------------------°--------------------°

[-- Attachment #2: loop.c.diff --]
[-- Type: text/plain, Size: 346 bytes --]

--- loop.c.old	Thu Sep 12 21:19:40 2002
+++ loop.c	Thu Sep 12 21:19:56 2002
@@ -1054,10 +1054,10 @@
 	printk(KERN_INFO "loop: loaded (max %d devices)\n", max_loop);
 	return 0;
 
-out_sizes:
-	kfree(loop_dev);
 out_blksizes:
 	kfree(loop_sizes);
+out_sizes:
+	kfree(loop_dev);
 	printk(KERN_ERR "loop: ran out of memory\n");
 	return -ENOMEM;
 }

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-09-13  3:25 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-12 20:28 [2.4.19] [2.4.20-pre6] loop.c memory allocation & freeing problem Yann E. MORIN

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.