summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2004-05-06 09:54:36 +0000
committerEric Andersen <andersen@codepoet.org>2004-05-06 09:54:36 +0000
commit32daaa2b2f83f60584bf50173be6f31728ba62c6 (patch)
tree9cf0866723d3592ecfaa36911950218466539abb
parent6fb11d57cf6f02bf4e9186d3264b86122b7dd52c (diff)
downloadbuildroot-novena-32daaa2b2f83f60584bf50173be6f31728ba62c6.tar.gz
buildroot-novena-32daaa2b2f83f60584bf50173be6f31728ba62c6.zip
Chris Wilson writes:
i Erik, I think I found a small bug in your cramfs patch, which I guess you ported from mkfs.jffs2.c. Therefore this bug might apply to mkfs.jffs2.c as well. When searching for a file (or device node) to create in a subdirectory, mkcramfs doesn't remove the parent's path component which it's already matched. This prevents the sought node from ever being found if it lives in a subdirectory.
-rw-r--r--sources/cramfs.patch2
1 files changed, 1 insertions, 1 deletions
diff --git a/sources/cramfs.patch b/sources/cramfs.patch
index 1f6f01556..884eb8cb8 100644
--- a/sources/cramfs.patch
+++ b/sources/cramfs.patch
@@ -828,7 +828,7 @@
+ /* Looks like we found a parent of the correct path */
+ if (name[len] == '/') {
+ if (e->child) {
-+ return (find_filesystem_entry (e, name, type));
++ return (find_filesystem_entry (e, name + len + 1, type));
+ } else {
+ return NULL;
+ }