linux-kernel - Re: util-linux: orphan

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: <200612271939.48125.arnd@arndb.de>
Date:	Wed, 27 Dec 2006 19:39:47 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Karel Zak <kzak@...hat.com>
Cc:	linux-kernel@...r.kernel.org, Henne Vogelsang <hvogel@...e.de>,
	Olaf Hering <olh@...e.de>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: util-linux: orphan

On Wednesday 27 December 2006 19:15, Karel Zak wrote:
> 
> On Wed, Dec 27, 2006 at 03:46:10AM +0100, Arnd Bergmann wrote:
> > On Monday 18 December 2006 08:17, Karel Zak wrote:
> > >         - remove FS/device detection code
> > >           (libblkid from e2fsprogs or libvolumeid is replacement)
> > 
> > I saw that the current Fedora already dynamically links /bin/mount
> > against /usr/lib/libblkid.so. 
> 
>  Sorry, but it's nonsense.
> 
>  $ grep -r %{_root_libdir}/libblkid.so *
> 
>  devel/e2fsprogs.spec:%{_root_libdir}/libblkid.so.*

Right, please accept my apologies for spreading confusion about this.
I currently don't have access to the machine that broke, so I could
not check the exact problem, and must have misremembered the bug.

> > This obviously does not work if /usr is a separate partition that
> > needs to be mounted with /bin/mount.
> 
>  Yes, I have /usr on a separate partition for many years :-)
>
> > I'd suggest that you make sure that mount always gets statically linked
> > against libblkid to avoid these problems.
> 
>  It's dynamically linked in many distributions without a problem.

The problem that I saw was because of selinux going wild. Statically linking
would have avoided the problem for me, but I guess this is just one
more reason for me to disable selinux and be done with it.

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/