From 32daaa2b2f83f60584bf50173be6f31728ba62c6 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Thu, 6 May 2004 09:54:36 +0000 Subject: [PATCH] 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. --- sources/cramfs.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/cramfs.patch b/sources/cramfs.patch index 1f6f01556e..884eb8cb83 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; + } -- 2.30.2