On 4-10-12 10:05 AM, Josip Rodin wrote:
On Tue, Oct 02, 2012 at 02:47:26PM +0200, Miquel van Smoorenburg wrote:
Package: freeradius
Version: 2.1.12+dfsg-1.1
Severity: important
Freeradius can dynamically grow and shrink its thread pool. When
growing the thread pool, multiple threads will call perl_clone
at the same time, which can result in segfaults. The call to
perl_clone should be protected with a mutex.
This was reported in
http://lists.freeradius.org/pipermail/freeradius-devel/2011-November/006568.html
and the patch was integrated for the 2.2.0 release. There hasn't
been a 2.1.x release with this patch yet.
The patch for 2.1.x is here:
https://github.com/alandekok/freeradius-server/commit/ecb3cd1dbedb764ab98532dae5e0b5bfc9571b00
Did you intend to file this as important and not serious or?
I wasn't sure. We are hitting this problem in production, but if you
don't use rlm_perl freeradius works fine otherwise.
So for freeradius in total I'd say "a bug which has a major effect on
the usability of a package, without rendering it completely unusable to
everyone.", while for the rlm_perl module it would be more like "it
makes the package unsuitable for release."
Perhaps I should have tagged it "serious", it can always be downgraded
if the maintainer doesn't agree, right?
Mike.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
