erofs-utils: lib: add support for symlink file in erofs_ilookup()
PATCH 1/1 erofs-utils: lib: add support for symlink file in erofs_ilookup()
When the path contains symbolic links, erofs_ilookup() does not function properly. This adds support for symlink files.
--- lib/namei.c | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-)
lib/namei.c +24 -1
@@ -195,6 +195,22 @@ struct nameidata {unsigned int ftype; }; +static int link_path_walk (const char *name,struct nameidata *nd); + +static int step_into_link (struct nameidata *nd,struct erofs_inode *vi) +{ +char buf[EROFS_MAX_BLOCK_SIZE ]; +int err; + +if (vi->i_size >EROFS_MAX_BLOCK_SIZE ) +return -EINVAL ; +memset (buf,0 ,sizeof (buf)); + err =erofs_pread (vi, buf, vi->i_size,0 ); +if (err) +return err; +return link_path_walk (buf, nd); +} +int erofs_namei (struct nameidata *nd,const char *name,unsigned int len) {erofs_nid_t nid = nd->nid;
@@ -233,6 +249,11 @@ int erofs_namei(struct nameidata *nd, const char *name, unsigned int len)return PTR_ERR (de);if (de) { + vi.nid = de->nid; + ret =erofs_read_inode_from_disk (&vi); +if (S_ISLNK (vi.i_mode)) { +return step_into_link (nd, &vi); + } nd->nid =le64_to_cpu (de->nid);return 0 ; }
@@ -243,7 +264,8 @@ int erofs_namei(struct nameidata *nd, const char *name, unsigned int len)static int link_path_walk (const char *name,struct nameidata *nd) { - nd->nid = nd->sbi->root_nid; +if (*name =='/' ) + nd->nid = nd->sbi->root_nid;while (*name =='/' ) name++;
@@ -274,6 +296,7 @@ int erofs_ilookup(const char *path, struct erofs_inode *vi)int ret;struct nameidata nd = { .sbi = vi->sbi }; + nd.nid = nd.sbi->root_nid; ret =link_path_walk (path, &nd);if (ret)return ret;
Signature · 1 line
2.43.5
Quoted 2 lines · Hongzhen Luo
When the
pathcontains symbolic links,erofs_ilookup()does not function properly. This adds support for symlink files.
Can you explain what's the use cases of this patch?
It seems both erofsfuse and fsck.erofs --extract don't need this.
Quoted 13 lines
Signed-off-by Hongzhen Luo <[email protected]>--- lib/namei.c | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-)lib/namei.c +0
-0@@ -195,6 +195,22 @@ struct nameidata {unsigned int ftype; };
lib/namei.c struct nameidata { · line 206
Quoted 10 lines
lib/namei.c +9
-0+static int link_path_walk (const char *name,struct nameidata *nd); + +static int step_into_link (struct nameidata *nd,struct erofs_inode *vi) +{ +char buf[EROFS_MAX_BLOCK_SIZE ]; +int err; + +if (vi->i_size >EROFS_MAX_BLOCK_SIZE ) +return -EINVAL ;
No, symlink size is independent to EROFS_MAX_BLOCK_SIZE, currently it's hard-code as 4096.
Quoted 11 lines
lib/namei.c +7
-0+memset (buf,0 ,sizeof (buf)); + err =erofs_pread (vi, buf, vi->i_size,0 ); +if (err) +return err; +return link_path_walk (buf, nd); +} +int erofs_namei (struct nameidata *nd,const char *name,unsigned int len) {erofs_nid_t nid = nd->nid;
lib/namei.c int erofs_namei(struct nameidata *nd, const char *name, unsigned int len) · line 256
Quoted 8 lines
lib/namei.c +5
-0@@ -233,6 +249,11 @@ int erofs_namei(struct nameidata *nd, const char *name, unsigned int len)return PTR_ERR (de);if (de) { + vi.nid = de->nid; + ret =erofs_read_inode_from_disk (&vi); +if (S_ISLNK (vi.i_mode)) { +return step_into_link (nd, &vi); + }
Why need brace here?
Thanks,
Gao Xiang
Quoted 10 lines · Gao Xiang
Quoted 2 lines · Hongzhen Luo
When the
pathcontains symbolic links,erofs_ilookup()does not function properly. This adds support for symlink files.Can you explain what's the use cases of this patch?
It seems both erofsfuse and fsck.erofs --extract don't need this.
Some third-party applications (such as Alibaba DADI) require obtaining block mapping information of files based on their paths using liberofs. When file paths include symbolic links, the current erofs_ilookup() function fails to correctly locate the inode. This submission enhances erofs_ilookup()'s support for symbolic link files.
Quoted 17 lines
Quoted 17 lines
Signed-off-by Hongzhen Luo <[email protected]>---
lib/namei.c| 25 ++++++++++++++++++++++++-1 file changed, 24 insertions(+), 1 deletion(-)lib/namei.c +3
-0@@ -195,6 +195,22 @@ struct nameidata { unsigned int ftype; }; +static int link_path_walk(const char *name, struct nameidata *nd); + +static int step_into_link (struct nameidata *nd,struct erofs_inode *vi) +{
Quoted 9 lines
lib/namei.c struct nameidata { · line 206
Quoted 5 lines
lib/namei.c +5
-0+ char buf[EROFS_MAX_BLOCK_SIZE]; + int err; + + if (vi->i_size > EROFS_MAX_BLOCK_SIZE) + return -EINVAL;No, symlink size is independent to
EROFS_MAX_BLOCK_SIZE, currently it's hard-code as 4096.
Okay, I will make the corresponding modifications in the next version.
Quoted 13 lines
Quoted 13 lines
lib/namei.c +7
-0+ memset(buf, 0, sizeof(buf)); + err = erofs_pread(vi, buf, vi->i_size, 0); + if (err) + return err; + return link_path_walk(buf, nd); +} + int erofs_namei(struct nameidata *nd, const char *name, unsigned int len) { erofs_nid_t nid = nd->nid;@@ -233,6 +249,11 @@ int erofs_namei(struct nameidata *nd, const char *name, unsigned int len) return PTR_ERR(de);
Quoted 8 lines
lib/namei.c int erofs_namei(struct nameidata *nd, const char *name, unsigned int len) · line 256
Quoted 6 lines
lib/namei.c +5
-0if (de) { + vi.nid = de->nid; + ret = erofs_read_inode_from_disk(&vi); + if (S_ISLNK(vi.i_mode)) { + return step_into_link(nd, &vi); + }Why need brace here?
Yes, the braces are not necessary, and I will clean them up later.
Quoted 3 lines
Thanks,
Gao Xiang
---
Thanks,
Hongzhen Luo
Quoted 5 lines · Hongzhen Luo
Quoted 3 lines · Gao Xiang
On 2024/8/11 16:09, Hongzhen Luo wrote:
Quoted 8 lines
Quoted 7 lines
Quoted 2 lines
When the
pathcontains symbolic links,erofs_ilookup()does not function properly. This adds support for symlink files.Can you explain what's the use cases of this patch?
It seems both erofsfuse and fsck.erofs --extract don't need this.
Some third-party applications (such as Alibaba DADI) require obtaining block mapping information of files based on their paths using liberofs. When file paths include symbolic links, the current
erofs_ilookup()function fails to correctly locate the inode. This submission enhances erofs_ilookup()'s support for symbolic link files.
Why it cannot be implemented in the application itself? Following block mapping and obtain the symlinked file block mapping is weird for erofs itself to resolve.
Thanks,
Gao Xiang
Quoted 15 lines · Gao Xiang
Quoted 12 lines · Hongzhen Luo
Quoted 10 lines · Gao Xiang
Quoted 2 lines · Hongzhen Luo
When the
pathcontains symbolic links,erofs_ilookup()does not function properly. This adds support for symlink files.Can you explain what's the use cases of this patch?
It seems both erofsfuse and fsck.erofs --extract don't need this.
Quoted 8 lines
Quoted 1 line
Some third-party applications (such as Alibaba DADI) require obtaining block mapping information of files based on their paths using liberofs. When file paths include symbolic links, the current
erofs_ilookup()function fails to correctly locate the inode. This submission enhances erofs_ilookup()'s support for symbolic link files.Why it cannot be implemented in the application itself? Following block mapping and obtain the symlinked file block mapping is weird for erofs itself to resolve.
Thanks,
Gao Xiang
That makes sense. Thanks for pointing it out, and please disregard this patch.
---
Thanks,
Hongzhen Luo