On Sat, 14 May 2005 08:22:56, GOTO Masanori wrote:
> I have not reappeared sysklogd breakage yet, but IMHO this problem is
> potentially existed - I agreed Miquel's proposal. Miquel, did you
> confirm this problem using sysklogd? If this patch fixes this bug, I
> think we should do NMU for sarge.
At Wed, 4 May 2005 14:11:38 +0200,
Miquel van Smoorenburg wrote:
> Christian Hammers wrote:
> > For what it's worth, I also tried Miguel's ctime-hang.c on both a Sarge i386
> > and a Sid amd64 machine with 2.6 kernels and can reproduce the hang in
> > 10 of 10 attempts.
>
> I also re-ran the ctim
Christian Hammers wrote:
> For what it's worth, I also tried Miguel's ctime-hang.c on both a Sarge i386
> and a Sid amd64 machine with 2.6 kernels and can reproduce the hang in
> 10 of 10 attempts.
I also re-ran the ctime-hang.c test program on i386 uniprocessor
and SMP, and amd64 SMP (all up-to-
For what it's worth, I also tried Miguel's ctime-hang.c on both a Sarge i386
and a Sid amd64 machine with 2.6 kernels and can reproduce the hang in
10 of 10 attempts.
bye,
-christian-
$ strace -e trace=\!time ./a.out
...
set_thread_area({entry_number:-1 -> 6, base_addr:0x401522a0, limit:1048575
I ran Miquel's ctime-hang.c, on a sarge machine with a 2.6 kernel, but
it kept on running for many minutes (that is, the SIGALRM happened all
the time). This didn't seem like a lockup. Did I do something wrong in
my attempt to reproduce this?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Thu, 2005-03-31 at 09:31 -0500, Jeff Bailey wrote:
> Miguel,
>
> I was looking through the sysklogd patch that you provided, and looked
> through the glibc code. I don't see any __libc_lock magic happening.
ctime() -> localtime() -> __tz_convert() -> __libc_lock_lock()
> Since ctime isn't
Miguel,
I was looking through the sysklogd patch that you provided, and looked through the glibc code. I don't see any __libc_lock magic happening. Since ctime isn't reentrant, no effort is made to protect the coder against threaded programming. I also checked the 'time' function in case yo
Package: sysklogd
Version: 1.4.1-16
Severity: grave
Justification: breaks the whole system
References:
http://lkml.org/lkml/2005/3/26/37
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=103392
http://lkml.org/lkml/2004/12/21/208
http://lkml.org/lkml/2004/11/2/17
Syslogd can hang if do
8 matches
Mail list logo