From: Artem Bityutskiy <dedekind1@gmail.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: joern <joern@logfs.org>,
linux-mtd <linux-mtd@lists.infradead.org>, arnd <arnd@arndb.de>,
Alex Dubov <oakad@yahoo.com>
Subject: Re: Few problems in mtd system
Date: Thu, 07 Jan 2010 09:11:21 +0200 [thread overview]
Message-ID: <1262848281.21915.42.camel@localhost> (raw)
In-Reply-To: <1261342795.4798.14.camel@maxim-laptop>
On Sun, 2009-12-20 at 22:59 +0200, Maxim Levitsky wrote:
> Folks, could you review my other questions about bugs in mtd core, and
> tell your opinion?
The MTD subsystem is nor very inhabitant these days, so you are mostly
on your own. I think you should just try fixing the issues you found,
test them, be careful, and send patches.
I believe MTD subsystem have many issues with "hotpluggable" devices
like your card, simply because no one probably worked seriously on this.
Most MTD devices are on-board chips, so few people care about
plugability.
> Yet another problem I found is inside add_mtd_blktrans_dev.
> This function takes mtd_table_mutex but never releases it.
> This sounds fishy, and deadlocks when it calls 'add_disk(gd);'
> This function (I think in case partitions are detected on device)
opens
> block device, and this takes that lock too
> (blktrans_open->get_mtd_device)>
I vaguely remember there was a fix for this, may be in 2.6.33-rcX ?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-01-07 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 22:08 Few problems in mtd system Maxim Levitsky
2009-12-19 17:17 ` Maxim Levitsky
2009-12-19 21:06 ` Maxim Levitsky
2009-12-19 21:58 ` Alex Dubov
2009-12-20 20:59 ` Maxim Levitsky
2009-12-21 14:00 ` Jörn Engel
2009-12-22 18:03 ` Maxim Levitsky
2009-12-22 20:32 ` Michael Trimarchi
2009-12-22 21:42 ` Maxim Levitsky
2009-12-22 23:39 ` Michael Trimarchi
2009-12-23 16:18 ` Maxim Levitsky
2010-01-07 7:11 ` Artem Bityutskiy [this message]
2010-01-07 16:16 ` Maxim Levitsky
2010-01-08 6:17 ` Jörn Engel
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=1262848281.21915.42.camel@localhost \
--to=dedekind1@gmail.com \
--cc=arnd@arndb.de \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@gmail.com \
--cc=oakad@yahoo.com \
/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.