Re: plperl sigfpe reset can crash the server

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>
Subject: Re: plperl sigfpe reset can crash the server
Date: 2012-08-24 22:19:23
Message-ID: 201208250019.23186.andres@2ndquadrant.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Saturday, August 25, 2012 12:15:00 AM Alex Hunsaker wrote:
> On Fri, Aug 24, 2012 at 4:10 PM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:
> > We probably should workaround that bug anyway given that its a pretty
> > trivial DOS using only a trusted language and it will take quite some
> > time to push out newer perl versions even if that bug gets fixed.
> >
> > Doing a pqsignal(SIGFPE, FloatExceptionHandler) after PERL_SYS_INIT3
> > seems to work. Is that acceptable?
>
> Makes sense to me. (I have not looked to see if there is some perl
> knob we can flip for this)
I couldn't find any. After some macro indirection the signal() call ends up
being done unconditionally by a compiled function (Perl_sys_init3) without any
conditions, so I don't think there is much that can be done without changing
perl's source code...

Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2012-08-24 22:36:34 PATCH: optimized DROP of multiple tables within a transaction
Previous Message Alex Hunsaker 2012-08-24 22:15:00 Re: plperl sigfpe reset can crash the server