linux-ext4 - libcom_err DSO version bump needed for 1.42?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Aug 2012 17:48:12 -0400
From:	"Brian J. Murrell" <brian@...erlinx.bc.ca>
To:	linux-ext4@...r.kernel.org
Subject: libcom_err DSO version bump needed for 1.42?

Hi,

I noticed when trying to upgrade my e2fsprogs RPM set from a 1.41.12ish
release to a 1.42.3ish release only e2fsprogs and e2fsprogs-libs got
upgraded and libcom_err didn't get upgraded despite there being ABI
differences between 1.41.12 and 1.42.3.  This results in the following
type of error:

# e2fsck
e2fsck: symbol lookup error: e2fsck: undefined symbol: set_com_err_gettext
# mke2fs 
mke2fs: symbol lookup error: mke2fs: undefined symbol: set_com_err_gettext

This appears to be due to the addition of set_com_err_gettext()  (in
4259052093da329907e255b11bf3e799872828c7) during the 1.42 development
cycle.

Since this addition introduces an ABI incompatibility in libcom_err,
isn't the process supposed to be to increase the SO's version so that
the tools find the proper version of the library and also so that it
gets upgraded accordingly by RPM with it's autoprovides/requires bits?

Cheers,
b.

Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)