All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongzhen Luo <hongzhen@linux.alibaba.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: lib: add support for symlink file in erofs_ilookup()
Date: Mon, 12 Aug 2024 11:14:35 +0800	[thread overview]
Message-ID: <19da3c76-b44f-4377-a653-e3e9d76966de@linux.alibaba.com> (raw)
In-Reply-To: <2b831007-f633-439c-b8a1-287b6658c6bf@linux.alibaba.com>


On 2024/8/12 11:03, Gao Xiang wrote:
>
>
> On 2024/8/12 10:50, Hongzhen Luo wrote:
>>
>> On 2024/8/12 10:24, Gao Xiang wrote:
>>>
>>>
>>> On 2024/8/11 16:09, Hongzhen Luo wrote:
>>>> When the `path` contains 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

That makes sense. Thanks for pointing it out, and please disregard this 
patch.

---

Thanks,

Hongzhen Luo


      reply	other threads:[~2024-08-12  3:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11  8:09 [PATCH] erofs-utils: lib: add support for symlink file in erofs_ilookup() Hongzhen Luo
2024-08-12  2:24 ` Gao Xiang
2024-08-12  2:50   ` Hongzhen Luo
2024-08-12  3:03     ` Gao Xiang
2024-08-12  3:14       ` Hongzhen Luo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19da3c76-b44f-4377-a653-e3e9d76966de@linux.alibaba.com \
    --to=hongzhen@linux.alibaba.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.