Hi,
i wrote:
> > Truncation nowadays has to take into respect that UTF-8 may
> > consist of multiple bytes and should avoid to leave incomplete
> > byte sequences.
> > (Does the kernel have a function for this ?)
Jan Kara wrote:
> Well, such truncation function would have to be specific to
Hi,
thanks for detailed reports. For now I did some research on the case of
file name truncation.
> ===
> "fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes length"
>
Hi,
during regression tests with libisofs i found two bugs
in fs/isofs, which i reported to Debian
"fs/isofs/util.c iso_date() will map years >= 2028 to 1970"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627
"fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes
Hi,
i wrote:
> > Truncation nowadays has to take into respect that UTF-8 may
> > consist of multiple bytes and should avoid to leave incomplete
> > byte sequences.
> > (Does the kernel have a function for this ?)
Jan Kara wrote:
> Well, such truncation function would have to be specific to
Hi,
during regression tests with libisofs i found two bugs
in fs/isofs, which i reported to Debian
"fs/isofs/util.c iso_date() will map years >= 2028 to 1970"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627
"fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes
Hi,
thanks for detailed reports. For now I did some research on the case of
file name truncation.
> ===
> "fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes length"
>
6 matches
Mail list logo