From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
"Alex Dubov" <oakad@yahoo.com>, arnd <arnd@arndb.de>
Subject: Re: Few problems in mtd system
Date: Tue, 22 Dec 2009 21:32:53 +0100 [thread overview]
Message-ID: <4B312CF5.3080709@gandalf.sssup.it> (raw)
In-Reply-To: <1261505034.8347.6.camel@maxim-laptop>
Maxim Levitsky wrote:
> On Mon, 2009-12-21 at 15:00 +0100, Jörn Engel wrote:
>
>> On Sun, 20 December 2009 22:59:55 +0200, Maxim Levitsky wrote:
>>
>>> I suspect that older non type M cards didn't have such emulation, but
>>> were real nand chips, bacause there are some references on the web about
>>> using XD card as a nand chip replacement.
>>> Such card as I have will really will make very poor nand replacement...
>>>
>> If you want to know whether the cards or the readers are to blame, you
>> can try to buy an old alauda reader on ebay. It is too slow to be
>> useful for most purposes, but I believe it did give me full access with
>> my cards.
>>
>>
>>> Folks, could you review my other questions about bugs in mtd core, and
>>> tell your opinion?
>>>
>
> I have several problems, more correctly bugs in mtd system I have to fix
> to make my driver work.
>
> Lets start from the problem I face now.
>
> Problem is that add_mtd_blktrans_dev is called with mtd_table_mutex
> locked, but it calls add_disk which opens the block device if you
> specify that you need partitions on the disk. Open routine 'looks' at
> mtd table using get_mtd_device, and thus deadlocks.
>
> Do you have a clue how to fix that so it won't break anything?
>
I try to follow the call, can you send the block stack trace?
just change the lock on get_mtd_device with a try_lock and BUG on
if it is taken
Michael
>
> Best regards,
> Maxim Levitsky
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2009-12-22 20:33 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 [this message]
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
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=4B312CF5.3080709@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox