From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: tglx@linutronix.de
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: bugreport
Date: Tue, 27 Jul 2004 18:40:38 +0400 [thread overview]
Message-ID: <41066966.8070107@yandex.ru> (raw)
In-Reply-To: <1090934568.20889.162.camel@thomas.tec.linutronix.de>
Thomas Gleixner wrote:
> On Tue, 2004-07-27 at 15:08, Artem B. Bityuckiy wrote:
>
>>Hello.
>>
>>There is a bug in jffs2 module registration function - super.c line 293:
>>the init_jffs2_fs function doesn't properly perform
>>the de-initialization in case of failures on lines 315 and 321.
>>The jffs2_inode_cachep is also not feed.
>>
>>I Tried to send a patch bit mailman soesn't gieve me...
>
>
> I think you meant that one, right ?
>
> Thanks, fixed in CVS
>
> tglx
>
>
> @@ -330,6 +330,7 @@
> out_compressors:
> jffs2_compressors_exit();
> out:
> + kmem_cache_destroy(jffs2_inode_cachep);
> return ret;
> }
>
Not only. The "go out" in case of jffs2_compressors_init() failure
doesn't free /proc resources...
I tried to send the following patch as the attached file (now I'll try
to just insert the text):
-- super.c 2004-07-18 18:44:42.000000000 +0400
+++ /home/dedekind/tmp/super_fixed.c 2004-07-26 15:05:34.000000000 +0400
@@ -318,7 +318,7 @@
ret =
if (ret) {
printk(KERN_ERR "JFFS2 error: Failed to initialise compressors\n");
- goto out;
+ goto out_proc;
}
ret = jffs2_create_slab_caches();
if (ret) {
@@ -336,10 +336,12 @@
jffs2_destroy_slab_caches();
out_compressors:
jffs2_compressors_exit();
+ out_proc:
#ifdef CONFIG_JFFS2_PROC
jffs2_proc_exit();
#endif
out:
+ kmem_cache_destroy(jffs2_inode_cachep);
return ret;
}
Note - the patch is just to show the problem and doesn't pretent to be
applied as is.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2004-07-27 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 13:08 bugreport Artem B. Bityuckiy
2004-07-27 13:22 ` bugreport Thomas Gleixner
2004-07-27 14:40 ` Artem B. Bityuckiy [this message]
2004-07-27 17:31 ` bugreport Thomas Gleixner
2004-07-28 6:41 ` bugreport Artem B. Bityuckiy
2004-07-29 19:56 ` bugreport David Woodhouse
[not found] <AMDPR08MB11409C5DC2EA9B3D8C71FC12BED82A@AMDPR08MB11409.eurprd08.prod.outlook.com>
2026-01-11 17:05 ` Bugreport do Carmo Lucas, Dr. Amilcar (T-PSC)
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 13:25 Bugreport Frank Schwidom
2024-01-19 23:14 ` Bugreport brian m. carlson
2023-10-24 20:40 bugreport galo joel
2023-11-20 8:36 ` bugreport Thomas Guyot
2020-12-02 10:08 bugreport Ole M
2020-12-02 16:25 ` bugreport Stefan Haller
2012-09-18 13:13 bugreport Dmitriy Bukach
2005-04-12 18:11 Bugreport Amelia Nilsson
2005-04-12 22:21 ` Bugreport Chris Wright
2004-07-26 11:16 bugreport Artem Bityuckiy
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=41066966.8070107@yandex.ru \
--to=abityuckiy@yandex.ru \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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.