Control: severity -1 important

On Sat, Dec 30, 2017 at 03:48:07PM +0300, Anatoly Pugachev wrote:
> Package: klibc-utils
> Version: 2.0.4-10
> Severity: normal
>
> Dear Maintainer,
>
> Upgrading klibc-utils from 2.0.4-9 to 2.0.4-10 started to produce sigserv in 
> fstype
>
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>
> using latest version 2.0.4-10 :
>
> $ dpkg -l klibc-utils
> ||/ Name                               Version                Architecture    
>        Description
> +++-==================================-======================-======================-=========================================================================
> ii  klibc-utils                        2.0.4-10               sparc64         
>        small utilities built with klibc for early boot
>
> $ /usr/lib/klibc/bin/fstype
> Segmentation fault (core dumped)
>
> $ sudo /usr/lib/klibc/bin/fstype /dev/vdiska2
> Segmentation fault
>
> I tried with upstream klibc.git repo, but getting sigserv as well, and since
> klibc.git does not have changed files almost a year now, not sure gdb 
> backtrace
> could be relevant, please see
> http://www.zytor.com/pipermail/klibc/2017-December/003965.html
>
>
>    * What outcome did you expect instead?
>
> using older package version of 2.0.4-9 :
>
> # dpkg -i *.deb
> dpkg: warning: downgrading klibc-utils from 2.0.4-10 to 2.0.4-9
> (Reading database ... 68475 files and directories currently installed.)
> Preparing to unpack klibc-utils_2.0.4-9_sparc64.deb ...
> Unpacking klibc-utils (2.0.4-9) over (2.0.4-10) ...
> dpkg: warning: downgrading libklibc from 2.0.4-10 to 2.0.4-9
> Preparing to unpack libklibc_2.0.4-9_sparc64.deb ...
> Unpacking libklibc (2.0.4-9) over (2.0.4-10) ...
> Setting up libklibc (2.0.4-9) ...
> Setting up klibc-utils (2.0.4-9) ...
> root@ttip:~/1# exit
>
> mator@ttip:~/linux-2.6$ dpkg -L klibc-utils | grep fstype
> /usr/lib/klibc/bin/fstype
>
> mator@ttip:~/linux-2.6$ /usr/lib/klibc/bin/fstype
> stdin: Illegal seek
>
> mator@ttip:~$ dpkg -l klibc-utils
> ||/ Name                               Version                Architecture    
>        Description
> +++-==================================-======================-======================-=========================================================================
> ii  klibc-utils                        2.0.4-9                sparc64         
>        small utilities built with klibc for early boot
>
> mator@ttip:~$ sudo /usr/lib/klibc/bin/fstype /dev/vdiska2
> FSTYPE=ext4
> FSSIZE=15002910720

Please consider applying the patch forwarded upstream (linked in an
earlier control message) soon; this bug means that if the current
initramfs is updated, it will no longer boot, as run-init will segfault
in klibc. Given sparc64 is not a release architecture I can't make this
bug RC, otherwise I'd probably go for critical.

(To be clear, the issue is in 2.0.4-10 simply because that is the first
upload to happen since sparc64 has had PIE enabled by default in GCC)

Regards,
James

Reply via email to