All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@tac.ch>
To: Amin Azez <azez@ufomechanic.net>
Cc: Netfilter Developers <netfilter-devel@lists.netfilter.org>
Subject: Re: Fixed Re: iptables 1.3.1 crashes on iptables-restore
Date: Mon, 08 Aug 2005 18:19:21 +0200	[thread overview]
Message-ID: <42F78609.5070504@tac.ch> (raw)
In-Reply-To: <42F78246.3030302@ufomechanic.net>

> I'm waiting for all the fancy goods to get merged before I take that one.

They get merged into the next mm round I reckon, Linus won't pull until
2.6.13 is out the doors.

>>Invoke /lib/libc.so.6 like a command. It won't destroy your system but
>>it will display how your libc was crafted.
>> 
> GNU C Library stable release version 2.3.2, by Roland McGrath et al.
> Copyright (C) 2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
> Compiled by GNU CC version 3.2.2 20030222 (Red Hat Linux 3.2.2-5).
> Compiled on a Linux 2.4.20 system on 2003-03-13.
> Available extensions:
>         GNU libio by Per Bothner
>         crypt add-on version 2.1 by Michael Glad and others
>         linuxthreads-0.10 by Xavier Leroy
>         BIND-8.2.3-T5B
>         libthread_db work sponsored by Alpha Processor Inc
>         NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
> Thread-local storage support included.

I'm by no means a libc expert but how did you get infected with this
libc version? :). I was under the impression that TLS support wasn't
functional until NPTL was introduced in the 2.6.x era. To my knowledge
this could explain the TLS related crashes you were seeing. Any chance
of upgrading this libc of yours?

I could of course be totally wrong.

Best regards,
Roberto Nibali, ratz
-- 
-------------------------------------------------------------
addr://Rathausgasse 31, CH-5001 Aarau  tel://++41 62 823 9355
http://www.terreactive.com             fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG                       Wir sichern Ihren Erfolg
-------------------------------------------------------------

  reply	other threads:[~2005-08-08 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  3:46 iptables 1.3.1 crashes on iptables-restore Alexander Samad
2005-03-31  8:18 ` Roberto Nibali
2005-08-04 16:24   ` Amin Azez
2005-08-05 10:08     ` Amin Azez
2005-08-05 12:57       ` Fixed " Amin Azez
2005-08-05 13:22         ` Roberto Nibali
2005-08-08 15:45           ` Amin Azez
2005-08-08 15:56             ` Roberto Nibali
2005-08-08 16:03               ` Amin Azez
2005-08-08 16:19                 ` Roberto Nibali [this message]
2005-08-08 16:28                   ` Amin Azez
2005-08-08 16:46                     ` Roberto Nibali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F78609.5070504@tac.ch \
    --to=ratz@tac.ch \
    --cc=azez@ufomechanic.net \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.