Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: lib: support GNUTYPE_LONGNAME for tarerofs
Date: Mon, 17 Jul 2023 15:53:39 +0800	[thread overview]
Message-ID: <bd4657ff-dea8-9b37-625f-c5ecf6bd5518@linux.alibaba.com> (raw)
In-Reply-To: <20230717073531.43203-1-hsiangkao@linux.alibaba.com>



On 7/17/23 3:35 PM, Gao Xiang wrote:
> The 'L' entry is present in a header for a series of 1 or more 512-byte
> tar blocks that hold just the filename for a file or directory with a
> name over 100 chars.
> 
> Following that series is another header block, in the traditional form:
>    A header with type '0' (regular file) or '5' (directory), followed by
>    the appropriate number of data blocks with the entry data.
> 
> In the header for this series, the name will be truncated to the 1st 100
> characters of the actual name.
> 
> Cc: Jingbo Xu <jefflexu@linux.alibaba.com>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---
>  lib/tar.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/lib/tar.c b/lib/tar.c
> index 8edfe75..b62e562 100644
> --- a/lib/tar.c
> +++ b/lib/tar.c
> @@ -570,6 +570,14 @@ restart:
>  		if (ret)
>  			goto out;
>  		goto restart;
> +	} else if (th.typeflag == 'L') {
> +		free(eh.path);
> +		eh.path = malloc(st.st_size + 1);
> +		if (st.st_size != erofs_read_from_fd(tar->fd, eh.path,
> +						     st.st_size))
> +			goto invalid_tar;
> +		eh.path[st.st_size] = '\0';
> +		goto restart;
>  	} else if (th.typeflag == 'K') {
>  		free(eh.link);
>  		eh.link = malloc(st.st_size + 1);

LGTM.

Tested-by: Jingbo Xu <jefflexu@linux.alibaba.com>

-- 
Thanks,
Jingbo

      reply	other threads:[~2023-07-17  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  7:35 [PATCH] erofs-utils: lib: support GNUTYPE_LONGNAME for tarerofs Gao Xiang
2023-07-17  7:53 ` Jingbo Xu [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=bd4657ff-dea8-9b37-625f-c5ecf6bd5518@linux.alibaba.com \
    --to=jefflexu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox