All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: [SECURITY] Local Netfilter / IPTables IP Queue PID Wrap Flaw
Date: Tue, 3 Dec 2002 20:21:16 +0100	[thread overview]
Message-ID: <20021203202116.58e6d00a.arnt@c2i.net> (raw)
In-Reply-To: <Mutt.LNX.4.44.0212040025010.28607-100000@blackbird.intercode.com.au>

On Wed, 4 Dec 2002 00:29:11 +1100 (EST), 
James Morris <jmorris@intercode.com.au> wrote in message 
<Mutt.LNX.4.44.0212040025010.28607-100000@blackbird.intercode.com.au>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Just an update on this, someone has pointed out that the recommended
> 2.4.20 kernel has a ext3 data corruption bug (which fortunately will
> not affect most users).
> 
> The changset comments for the ext3 bug are at:
> <http://linux.bkbits.net:8080/linux-2.4/cset@1.793?nav=index.html|Cha
> ngeSet@-1d>
> 
> Please be careful if updating to 2.4.20, or wait until 2.4.21.

..and meanwhile alias 'umount' to 'sync && umount', 
you may want to chuck in a 'sleep 45' to play safer.

..url to a fix patch, anyone?


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.




  reply	other threads:[~2002-12-03 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 10:57 [SECURITY] Local Netfilter / IPTables IP Queue PID Wrap Flaw James Morris
2002-12-03 13:29 ` James Morris
2002-12-03 13:29 ` James Morris
2002-12-03 19:21   ` Arnt Karlsen [this message]
2002-12-04 10:28     ` Maciej Soltysiak
2002-12-04 19:49       ` Arnt Karlsen
2002-12-05 23:48       ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2002-12-03 10:57 James Morris

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=20021203202116.58e6d00a.arnt@c2i.net \
    --to=arnt@c2i.net \
    --cc=netfilter@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.