From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [PATCH] JFFS[23] slab corruption
Date: Wed, 05 Jan 2005 13:42:03 +0300 [thread overview]
Message-ID: <41DBC47B.4080003@yandex.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0501031923110.14981@phoenix.infradead.org>
Artem B. Bityuckiy wrote:
> Hi.
>
> There is slab corruption bug in JFFS2. Patch is attached.
>
> Problem:
> In jffs2_do_clear_inode() we call the jffs2_kill_fragtree() which kills
> the fragtree and mark the correspondent nodes obsolete.
>
> The jffs2_mark_node_obsolete function frees the inode's jffs2_inode_cache
> object when marks the last node obsolete (nodemngnt.c:594). But the
> f->inocache still points to this deleted object.
>
> Later in jffs2_do_clear_inode() we set the f->inocache state thus,
> corrupting the slab cache object which does not belong us anymore. I have
> seen several messages about the slab corruption.
>
> Ok to commit it ?
I'm sorry, I attached wrong file. Here is the patch:
RCS file: /home/cvs/mtd/fs/jffs2/readinode.c,v
retrieving revision 1.117
diff -u -r1.117 readinode.c
--- readinode.c 20 Nov 2004 18:06:54 -0000 1.117
+++ readinode.c 3 Jan 2005 19:24:41 -0000
@@ -688,7 +688,7 @@
jffs2_free_full_dirent(fd);
}
- if (f->inocache && f->inocache->state != INO_STATE_CHECKING)
+ if (!deleted && f->inocache->state != INO_STATE_CHECKING)
jffs2_set_inocache_state(c, f->inocache,
INO_STATE_CHECKEDABSENT);
up(&f->sem);
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-01-05 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 19:26 [PATCH] JFFS[23] slab corruption Artem B. Bityuckiy
2005-01-05 10:42 ` Artem B. Bityuckiy [this message]
2005-01-05 11:33 ` David Woodhouse
2005-01-05 14:13 ` Artem B. Bityuckiy
2005-02-27 10:30 ` David Woodhouse
2005-02-27 14:02 ` Artem B. 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=41DBC47B.4080003@yandex.ru \
--to=dedekind@yandex.ru \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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