This is the mail archive of the
mailing list for the glibc project.
Re: prlimit64: inconsistencies between kernel and userland
- From: Rich Felker <dalias at aerifal dot cx>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, David Daney <ddaney dot cavm at gmail dot com>, "Pinski, Andrew" <Andrew dot Pinski at caviumnetworks dot com>, Andreas Barth <aba at ayous dot org>, David Miller <davem at davemloft dot net>, aurelien at aurel32 dot net, linux-mips at linux-mips dot org, libc-alpha at sourceware dot org
- Date: Tue, 5 Nov 2013 18:55:05 -0500
- Subject: Re: prlimit64: inconsistencies between kernel and userland
- Authentication-results: sourceware.org; auth=none
- References: <20131104213756 dot GD18700 at hall dot aurel32 dot net> <20131104 dot 194519 dot 1657797548878784116 dot davem at davemloft dot net> <Pine dot LNX dot 4 dot 64 dot 1311050058580 dot 9883 at digraph dot polyomino dot org dot uk> <20131105012203 dot GA24286 at brightrain dot aerifal dot cx> <20131105085859 dot GE28240 at mails dot so dot argh dot org> <20131105183732 dot GB24286 at brightrain dot aerifal dot cx> <52793C50 dot 9030300 at gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1311052234420 dot 30260 at digraph dot polyomino dot org dot uk> <20131105223953 dot GG24286 at brightrain dot aerifal dot cx> <87ppqez9sh dot fsf at igel dot home>
On Wed, Nov 06, 2013 at 12:52:14AM +0100, Andreas Schwab wrote:
> Rich Felker <firstname.lastname@example.org> writes:
> > BTW, what happens on a distro where -dev packages are separate and the
> > user compiles with old headers (not having upgraded the dev package)
> > but new libc.so? :-)
> The devel package must either be self-contained or require the matching
> non-devel package.
That doesn't help. The problem is that the non-devel package gets
upgraded and ldconfig re-links the .so to the .so.X.Y.Z for the new
version. Really, the problem is ldconfig. If the .so link were
correctly created by the devel package, rather than by ldconfig, then
the headers and link-time library version would always match.
So, in short, ldconfig considered harmful.