Re: armhf version of bzip2 is broken
Hi.
On Mon, Nov 11, 2019 at 09:11:40PM +0100, Sven Joachim wrote:
> On 2019-11-11 22:22 +0300, Reco wrote:
>
> > Confirming, real debian armhf is affected. The problematic place is:
> >
> > $ strace -eopenat bzip2 -z 4038000640
> > ...
> > openat(AT_FDCWD, "4038000640", O_RDONLY) = -1 EOVERFLOW (Value too large for defined data type)
> >
> >
> > And EOVERFLOW in openat(2) is:
> >
> > pathname refers to a regular file that is too large to be opened. The
> > usual scenario here is that an application compiled on a 32-bit platform
> > without -D_FILE_OFFSET_BITS=64 tried to open a file whose size
> > exceeds (1<<31)-1 bytes; see also O_LARGEFILE above. This is the
> > error specified by POSIX.1; in kernels before 2.6.24, Linux gave the
> > error EFBIG for this case.
> >
> >
> > So, yep, you've found a bug in Debian packaging, consider filling it via
> > proper channels.
>
> Since I could reproduce the problem on i386, I have already done that:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944557.
Appreciate the effort, I'll subscribe to the bug.
Reco
Reply to: