public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: w@1wt.eu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.37.3
Date: Mon, 20 Jul 2009 11:48:00 +0400	[thread overview]
Message-ID: <4A642130.8030303@msgid.tls.msk.ru> (raw)
In-Reply-To: <20090719234914.GA3765@hera.kernel.org>

Willy Tarreau wrote:
> Linux 2.4.37.3 has just been released.
[]
> The second major issue concerns the r8169 driver. Approximately one
> month ago was revealed an issue with this driver, causing kernel
> panics and possibly more if too large frames were sent to the chip
> (CVE-2009-1389). 2.4 was not affected by the bug, but showed the
> same symptoms. It turned out that there were multiple issues with
> the setting of RX descriptors after reuse, and some recent 2.6
> fixes allowing automatic recovery were missing. So after two long
> days trying to figure out why that damn chip insisted in writing
> more bytes than allowed (and crashing my box), I could spot and
> fix the issues.
> 
> If there are 2.4 users with this cheap NIC, I strongly suggest that
> they upgrade, especially if they're used to encounter freezes or
> lack of network connectivity once in a while ; for others, well, do
> not buy that NIC.

The thing is that this very nic is used on-board on vast majority of
mainboards, at least in cheap- to mid-range price, for amd and intel
processors.  Also many notebooks use this chip series.  Several months
ago I were shopping for a mainboard with certain characteristics (I
needed 3 PCI ports and a way to plug some monitor, and support for 4
ECC DIMMs and recent Phenom processors) - it was difficult to find such
a combination alone, without additional constrains for !r8169 chip
(I finally bought Asus M3A-H/HDMI mobo with atl1 NIC, just by a chance).

/mjt

  reply	other threads:[~2009-07-20  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 23:49 Linux 2.4.37.3 Willy Tarreau
2009-07-20  7:48 ` Michael Tokarev [this message]
2009-07-20  9:31   ` Willy Tarreau

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=4A642130.8030303@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox