From: Adam Wozniak <adam.wozniak@comdev.cc>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: i node, u node, we all node for inodes
Date: Fri, 08 Feb 2002 10:31:54 -0800 [thread overview]
Message-ID: <3C64199A.2E61AB33@comdev.cc> (raw)
In-Reply-To: Pine.LNX.4.44.0202081054280.25850-100000@lapdancer.baythorne.internal
Is there some sort of "JFFS2 internals for dummies" guide around?
I'm seeing odd behavior that I can only attribute to linked lists
in RAM becoming corrupt, and I'd like to get a better understanding
of how each list is used, etc...
In the JFFS2 context...
Is the next_phys chain in the raw_node_ref null terminated?
Is the trick with the NULL member in the inode_cache guaranteed to
always work,
or just at boot time?
Can an inode have raw nodes in multiple erase blocks? If so, how is
this
represented in the raw_node_ref?
Does an inode have a fixed or maximum size?
Can a raw node contain data used by mutiple inodes? If not, what
prevents
this from happening?
Some basic definitions would be helpful.
--Adam
--
Adam Wozniak (KG6GZR) COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc 3450 Broad St. 107, San Luis Obispo, CA 93401
http://www.comdev.cc
Voice: (805) 544-1089 Fax: (805) 544-2055
next prev parent reply other threads:[~2002-02-08 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020207121316.8917.qmail@mailweb21.rediffmail.com>
2002-02-08 0:58 ` DOC firmware problems David Woodhouse
2002-02-08 18:31 ` Adam Wozniak [this message]
2002-02-08 18:30 ` i node, u node, we all node for inodes David Woodhouse
2002-02-08 19:08 ` Adam Wozniak
2002-02-09 1:28 ` David Woodhouse
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=3C64199A.2E61AB33@comdev.cc \
--to=adam.wozniak@comdev.cc \
--cc=dwmw2@infradead.org \
--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