Re: [Bug-tar] GNU tar 1.22 creating USTAR not readable by other TAR implementations

[Sergey Poznyakoff]

Kent Boortz <address@hidden> ha escrit:

> Some test results below with GNU TAR + the patch. I also added Solaris
> results as referense. Note that I do expect some of the below tests to
> fail, just trying out "border cases".

Thanks for the extensive testing.

> In some cases just the error message is a bit misleading.

What message are you referring to?

> So somehow both Solaris and GNU TAR has a 99 character limitation on
> the first directory part that it is to be put into "prefix", EXCEPT
> that GNU TAR seems to accept exactly 155 characts as well.

According to the standard (citing from the memory): the file pathname
is formed, if prefix is not an empty string (does not begin with \0),
by concatenating prefix (up to the first \0), a slash, and name field;
If prefix begins with \0, the name field is used alone.

When splitting the long file name for storing it in the header, the
reverse operation is performed.

See Tim's posting for the answers to the rest of your questions.

> The third line (1) triggers the bug again, making second header to
> have nothing in the "name" field.

Yes, indeed.  Thanks for reporting.

> Worse, in the test (1) the third record is corrupt, "name" is
> "cccc....bbbb...." with no "/", i.e. file name is wrong.

Can't reproduce this. In this case I get 100 'c' characters in the
name field and the correct prefix.  Can you send me the tar archive
you got in this step?

> Maybe it would be a good idea to include some sort of test suite for
> this with the GNU TAR sources?

Definitely, it is.

Regards,
Sergey