i node, u node, we all node for inodes

[David Woodhouse]

On Fri, 8 Feb 2002, Adam Wozniak wrote:

> Is there some sort of "JFFS2 internals for dummies" guide around?

Well, there was one here at linux.conf.au a few hours ago :)

> 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?

Yes.
> 
> Is the trick with the NULL member in the inode_cache guaranteed to
> always work, or just at boot time?

Always _except_ during boot time, when the NULL member is in fact used.

> Can an inode have raw nodes in multiple erase blocks?  If so, how is
> this represented in the raw_node_ref?

Yes. The raw_node_ref has a next_phys pointer pointing to the next 
physical node on the medium, and a next_in_ino pointer pointing to the 
next physical node belonging to the same inode. They're unrelated.

> Does an inode have a fixed or maximum size?

Do you mean a node? Not explicitly, although each type of node has its own 
limits so you could deduce the maximum node size you'll ever see.

> Can a raw node contain data used by mutiple inodes?  If not, what
> prevents this from happening?

Each node belongs to only one inode. It's generated for that inode, added 
to the list for that inode, the physical node on the flash contains the 
inode number. Why would it get shared?

-- 
dwmw2