netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <jianjun@zeuux.org>
To: jon.lin@vatics.com
Cc: davem@davemloft.net, dada1@cosmosbay.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.29.1 1/1] 8139too: fix HW initial flow
Date: Mon, 20 Apr 2009 21:28:00 +0800	[thread overview]
Message-ID: <20090420132800.GA9119@ubuntu> (raw)
In-Reply-To: <0E04AEADD178614A86F3017CC5FA693B4959924809@MS.vivotek.tw>

On Mon, Apr 20, 2009 at 08:58:01PM +0800, jon.lin@vatics.com wrote:
>From: Jonathan Lin <jon.lin@vatics.com>
>
>While ifconfig eth0 up kernel calls open() of 8139 driver(8139too.c).
>In rtl8139_hw_start() of rtl8139_open(), 8139 driver enable RX before setting up the DMA buffer address. In this interval where RX was enabled and DMA buffer address is not yet set up, any incoming broadcast packet would be send to a strange physical address:
>0x003e8800 which is the default value of DMA buffer address.
>Unfortunately, this address is used by Linux kernel. So kernel panics.
>This patch fix it by setting up DMA buffer address before RX enabled and everything is fine even under broadcast packets attack.
>
>Signed-off-by: Jonathan Lin <jon.lin@vatics.com>

Reviewed-by: Amos Kong <jianjun@zeuux.org>

>--- linux-2.6.29.1/drivers/net/8139too.c.orig   2009-04-19 17:50:38.000000000 +0800
>+++ linux-2.6.29.1/drivers/net/8139too.c        2009-04-19 17:52:51.000000000 +0800
>@@ -1382,6 +1382,10 @@ static void rtl8139_hw_start (struct net
>        RTL_W32_F (MAC0 + 0, le32_to_cpu (*(__le32 *) (dev->dev_addr + 0)));
>        RTL_W32_F (MAC0 + 4, le16_to_cpu (*(__le16 *) (dev->dev_addr + 4)));
>
>+       tp->cur_rx = 0;
>+       /* init Rx ring buffer DMA address BEFORE Rx enabled*/
>+       RTL_W32_F (RxBuf, tp->rx_ring_dma);
>+
...

  reply	other threads:[~2009-04-20 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 12:58 [PATCH 2.6.29.1 1/1] 8139too: fix HW initial flow jon.lin
2009-04-20 13:28 ` Amos Kong [this message]
2009-04-21  8:52 ` David Miller
2009-04-21  9:48   ` Amos Kong
2009-04-21 10:09     ` jon.lin
2009-04-21 10:34       ` Eric Dumazet
2009-04-21 10:30     ` Eric Dumazet
2009-04-22  7:44       ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-04-21 10:13 [PATCH 2.6.29.1 1/1]8139too:fix " User Tzungder
2009-04-19 10:16 [PATCH 2.6.29.1 1/1] 8139too: fix " Tzungder Lin
2009-04-19 11:22 ` Eric Dumazet
2009-04-20  1:54 ` Tzungder Lin
2009-04-20 10:14   ` David Miller

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=20090420132800.GA9119@ubuntu \
    --to=jianjun@zeuux.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=jon.lin@vatics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).