public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: catboat@texas.net
To: linux-mtd@lists.infradead.org
Subject: dynamic mtd_blktrans_dev not fully init'd under UBI?
Date: Fri, 30 Nov 2007 14:58:14 -0600	[thread overview]
Message-ID: <1196456294.47507966462cb@webmail.texas.net> (raw)



Hi all,

I have a UBI system, and I notice this causes a kernel panic.
Make a volume that does not previously exist, eg 50:

     ubimkvol -d0 -n50 -N vol50 -s 640000 
     cat /dev/mtdblock/vol50  >/dev/null 

I get a panic in mtdblockd as it handles the block
requests generated by cat. 

In older versions, the struct semaphore of mtd_blktrans_dev
is not initialized, so the kernel panics in __down. 

In the newest git, I see a mutex named "lock" instead, but 
I don't think it's initialized either. See the function 
mtdblock_add_mtd() in drivers/mtd/mtdblock.c. The struct
mtd_blktrans_dev is just kzalloc'd leaving the mutex lock
all zeroes. 

Can anybody recreate this? 

Monte Copeland
IBM Austin

             reply	other threads:[~2007-11-30 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 20:58 catboat [this message]
2007-12-01  9:28 ` dynamic mtd_blktrans_dev not fully init'd under UBI? David Woodhouse
2007-12-01 17:00   ` catboat

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=1196456294.47507966462cb@webmail.texas.net \
    --to=catboat@texas.net \
    --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