From: Thomas Chou <thomas@wytron.com.tw>
To: linux-mtd@lists.infradead.org
Subject: mkfs.jffs2 failed to create repeated dev nodes from device_table.txt
Date: Thu, 30 Dec 2010 15:31:49 +0800 [thread overview]
Message-ID: <4D1C3565.1030800@wytron.com.tw> (raw)
Hi experts,
I found an issue with the latest git head. The mkfs.jffs2 failed to
create repeated dev nodes from the device_table.txt in the git tree,
such as hda1-15, tty0-5.
It happened with this pattern,
/dev/tty c 666 0 0 5 0 0 0 -
/dev/tty c 666 0 0 4 0 0 1 6
# IDE Devices
/dev/hda b 640 0 0 3 0 0 0 -
/dev/hda b 640 0 0 3 1 1 1 15
/dev/hdb b 640 0 0 3 64 0 0 -
/dev/hdb b 640 0 0 3 65 1 1 15
Using jffs2dump -c, I could see only hda,
Dirent node at 0x004d3970, totlen 0x0000002b, #pino 14,
version 274, #ino 276, nsize 3, name hda
Inode node at 0x004d399c, totlen 0x00000046, #ino 276,
version 1, isize 0, csize 2, dsize 2, offset
0
Best regards,
Thomas
next reply other threads:[~2010-12-30 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 7:31 Thomas Chou [this message]
2010-12-31 1:45 ` [PATCH] mkfs.jffs2: fix repeated dev nodes Thomas Chou
2011-01-16 18:51 ` Artem Bityutskiy
2010-12-31 3:16 ` [PATCH] mkfs.jffs2: fix devtable count as mkfs.ubifs does Thomas Chou
2010-12-31 5:08 ` Mike Frysinger
2010-12-31 5:54 ` Thomas Chou
2011-01-16 18:51 ` Artem Bityutskiy
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=4D1C3565.1030800@wytron.com.tw \
--to=thomas@wytron.com.tw \
--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 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.