linux-ext4 - Re: [PATCH] configure: Disable libblkid by default

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090719212714.GA6886@nb.net.home>
Date:	Sun, 19 Jul 2009 23:27:14 +0200
From:	Karel Zak <kzak@...hat.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Scott James Remnant <scott@...ntu.com>, linux-ext4@...r.kernel.org,
	util-linux-ng@...r.kernel.org
Subject: Re: [PATCH] configure: Disable libblkid by default

 Hi Ted,

On Sun, Jul 19, 2009 at 07:56:17AM -0400, Theodore Tso wrote:
> Also, apparently no once noticed until now, but there's a bug in the
> util-linux-ng's uuid.sym file.  The uuid_pack and uuid_unpack symbols
> are missing, because someone forgot to include them in the uuid.sym
> file.

 is it really bug? Why do you want to export symbols that are not part
 of the library API? 

 I don't see uuid_pack and uuid_unpack in uuid.h. I guess nobody use
 these symbols ;-)

> BTW, **why** is util-linux-ng gratuitously introducing backwards
> incompatibility such that packages built with util-linux-ng won't work
> with the older shared libraries?   There's no reason to do this.

 Good point. I agree that (at first glance) there's no reason for this
 change. But...

     "If possible, projects implementing generally usable DSOs
     should use symbol versioning from day one."
              -- How To Write Shared Libraries, Ulrich Drepper

 I agree with Ulrich, symbol versioning is really really good thing.

 Unfortunately, it's not possible to combine versioned symbols with
 anonymous (without version) symbols. It means after first change to
 the library ABI we will need to introduce UUID_1.0 for old symbols.

 The move from e2fsprogs to util-linux-ng is excellent opportunity 
 to introduce ABI versioning to libuuid. I don't think this change has
 negative impact to our distributions in practice.

 How often people need to mix old libuuid (from e2fsprogs) with
 applications compiled against new libuuid (from util-linux-ng)? I
 guess almost never...

> Argh, util-linux-ng 2.16 has already been released; is it too late to
> undo this change?

 I think yes, it's too late.

 A new version (2.16.1) without UUID_1.0 will require mass rebuild in
 all distributions/systems where are libuuid applications with ABI
 versioning. IMHO this is much more painful that impossibility to
 downgrade to the old libuuid (from e2fsprogs).

 Maybe we can add --disable-{libuuid,libblkid}-versioning for people
 who need to bypass the default behaviour.

    Karel

-- 
 Karel Zak  <kzak@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html