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]

Date:	Mon, 20 Jul 2009 10:23:37 -0400
From:	Theodore Tso <tytso@....edu>
To:	Karel Zak <kzak@...hat.com>
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

On Sun, Jul 19, 2009 at 11:27:14PM +0200, Karel Zak wrote:
> 
> 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? 

You're right; I took a closer look at it, and they aren't part of the
library API.

>  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.

Yes, but I would have preferred to do so on a per symbol basis.  And
the UUID library isn't one that's likely to change in the future.

> > 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).

Sigh, you're probably right.

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

There are some commercial programs that might use libuuid --- minor
ones, like SAP R/3.  So they might want to create programs that work
on both RHEL 5 and RHEL 6.  The only way I can think of doing this is
to build the link libraries without the map file, and the shared
library with the map file.

	    	      	      	     	      - Ted
--
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