From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Keijiro Yano <keijiro_yano@yahoo.co.jp>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 mutex problem
Date: Tue, 15 Nov 2005 16:57:10 +0300 [thread overview]
Message-ID: <4379E936.6040309@yandex.ru> (raw)
In-Reply-To: <004d01c5e9ea$f9fccac0$0b01a8c0@YANO>
Keijiro Yano wrote:
> It is for Linux 2.6.10.
> But, based on my source level investigation, it can be applied for the
> latest CVS.
Ok.
> I have tested it only on Linux 2.6.10.
Ok.
> I think that ecos doesn't have this problem, because ecos initializes
> the locked mutex in jffs2_init_inode_info().
Hmm, I do you mean that Ecos's jffs2_init_inode_info() is not a slab
cache constructor so the bug does not exist there? Probably you're right.
Thanks. I think I'll commit this patch if people are OK.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-11-15 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 15:43 jffs2 mutex problem Keijiro Yano
2005-11-12 13:11 ` Artem B. Bityutskiy
2005-11-14 12:55 ` Keijiro Yano
2005-11-14 14:55 ` Artem B. Bityutskiy
2005-11-15 13:46 ` Keijiro Yano
2005-11-15 13:54 ` Josh Boyer
2005-11-15 13:57 ` Artem B. Bityutskiy [this message]
2005-11-24 16:28 ` Artem B. Bityutskiy
2005-11-25 15:17 ` Keijiro Yano
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=4379E936.6040309@yandex.ru \
--to=dedekind@yandex.ru \
--cc=keijiro_yano@yahoo.co.jp \
--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