On Sun, Mar 08, 2015 at 09:48:50PM +0100, Aurelien Jarno wrote:
> Thanks for your work, it's nice we have been able to understand the real
> issue.
Well I thing the best summary of the problem is that the aux-cache
handling code is awful and doesn't check anything before using the
incoming data as
control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=18093
On 2015-02-25 13:49, Lennart Sorensen wrote:
> I looked at ways the aux-cache could cause a segfault, and given the
> file is mmap'd and has data offsets in it that are used as pointers
> without being checked it is not ha
Processing control commands:
> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=18093
Bug #759530 [libc-bin] libc-bin: ldconfig breaks a system
Set Bug forwarded-to-address to
'https://sourceware.org/bugzilla/show_bug.cgi?id=18093'.
--
759530: http://bugs.debian.org/cgi-bin/bugrepor
On Sun, Mar 01, 2015 at 10:22:05PM +0100, Niels Thykier wrote:
> Excellent, thanks.
>
> I am taking the liberty of adding the patch tag for this one. If
> nothing else, I would greatly appreciate having ldconfig not seg. fault. :)
That makes sense to me.
> Sounds like the aux-cache could do wit
Control: tags -1 patch upstream
On Wed, 25 Feb 2015 13:49:00 -0500 "Lennart Sorensen"
wrote:
> I looked at ways the aux-cache could cause a segfault, and given the
> file is mmap'd and has data offsets in it that are used as pointers
> without being checked it is not hard to see how a corrupt fil
I looked at ways the aux-cache could cause a segfault, and given the
file is mmap'd and has data offsets in it that are used as pointers
without being checked it is not hard to see how a corrupt file could
cause a segfault. The following patch makes the segfaults I was able
to think of and create
6 matches
Mail list logo
