[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080118065204.1c999c08@osprey.hogchain.net>
Date: Fri, 18 Jan 2008 06:52:04 -0600
From: Jay Cliburn <jacliburn@...lsouth.net>
To: davem@...emloft.net
Cc: Jay Cliburn <jacliburn@...lsouth.net>, jeff@...zik.org,
csnook@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH] atl1: fix frame length bug
On Mon, 14 Jan 2008 20:04:28 -0600
Jay Cliburn <jacliburn@...lsouth.net> wrote:
> On Mon, 14 Jan 2008 19:56:41 -0600
> Jay Cliburn <jacliburn@...lsouth.net> wrote:
>
> > The driver sets up the hardware to accept a frame with max length
> > equal to MTU + Ethernet header + FCS + VLAN tag, but we neglect to
> > add the VLAN tag size to the ingress buffer. When a VLAN-tagged
> > frame arrives, the hardware passes it, but bad things happen
> > because the buffer is too small. This patch fixes that.
> >
> > Thanks to David Harris for reporting the bug and testing the fix.
> >
> > Tested-by: David Harris <david.harris@...i-inc.com>
> > Signed-off-by: Jay Cliburn <jacliburn@...lsouth.net>
>
> Jeff, Dave,
>
> This bugfix needs to go in for 2.6.24 if possible.
Dave,
I saw a message you sent awhile ago about Jeff handing off some netdev
stuff to you. Since I haven't seen anything to rescind that notice,
I'll direct my request to you.
Could you please merge this patch for 2.6.24?
http://article.gmane.org/gmane.linux.network/83368
When the reporter hits the bug, the result is a locked up kernel.
Granted, it's triggered only in the presence of VLAN tagged frames, but
it's a serious bug and the fix is simple.
Jay
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists