summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2006-05-19 00:28:49 +0100
committerDavid Woodhouse <dwmw2@infradead.org>2006-05-19 00:28:49 +0100
commitaef9ab47841af45888d950baa6448072cc70bdd5 (patch)
tree79545ddc225f64bc38fa04525ac4125c86202cb8 /include
parentf6a673b3f4f93c1c50e1b18f29254b0531b722a8 (diff)
downloadkernel-crypto-aef9ab47841af45888d950baa6448072cc70bdd5.tar.gz
kernel-crypto-aef9ab47841af45888d950baa6448072cc70bdd5.tar.xz
kernel-crypto-aef9ab47841af45888d950baa6448072cc70bdd5.zip
[JFFS2] Support new device nodes
Device node major/minor numbers are just stored in the payload of a single data node. Just extend that to 4 bytes and use new_encode_dev() for it. We only use the 4-byte format if we _need_ to, if !old_valid_dev(foo). This preserves backwards compatibility with older code as much as possible. If we do make devices with major or minor numbers above 255, and then mount the file system with the old code, it'll just read the first two bytes and get the numbers wrong. If it comes to garbage-collect it, it'll then write back those wrong numbers. But that's about the best we can expect. Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'include')
-rw-r--r--include/linux/jffs2.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/linux/jffs2.h b/include/linux/jffs2.h
index a26fbd498c7..007d76d290c 100644
--- a/include/linux/jffs2.h
+++ b/include/linux/jffs2.h
@@ -173,4 +173,10 @@ union jffs2_node_union
struct jffs2_unknown_node u;
};
+/* Data payload for device nodes. */
+union jffs2_device_node {
+ jint16_t old;
+ jint32_t new;
+};
+
#endif /* __LINUX_JFFS2_H__ */