[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080824020324.GA8762@xi.wantstofly.org>
Date: Sun, 24 Aug 2008 04:03:24 +0200
From: Lennert Buytenhek <buytenh@...tstofly.org>
To: netdev@...r.kernel.org
Cc: Dale Farnsworth <dale@...nsworth.org>,
Nicolas Pitre <nico@....org>, akpm@...l.org,
Gerhard Bertelsmann <info@...hard-bertelsmann.de>
Subject: [PATCH 0/5,RFC] mv643xx_eth fixes for 2.6.27
Hi,
The following five mv643xx_eth fixes for 2.6.27 since commit
6a55617ed5d1aa62b850de2cf66f5ede2eef4825:
Linus Torvalds (1):
Linux v2.6.27-rc4
are available in the git repository at:
git://git.marvell.com/mv643xx_eth.git for-2.6.27
http://git.marvell.com/?p=mv643xx_eth.git;a=summary
Lennert Buytenhek (5):
mv643xx_eth: fix NAPI 'rotting packet' issue
mv643xx_eth: fix double add_timer() on the receive oom timer
mv643xx_eth: fix inconsistent lock semantics
mv643xx_eth: fix NULL pointer dereference in rxq_process()
mv643xx_eth: enforce multiple-of-8-bytes receive buffer size restriction
drivers/net/mv643xx_eth.c | 33 +++++++++++++++++++--------------
1 files changed, 19 insertions(+), 14 deletions(-)
The second patch should fix http://bugzilla.kernel.org/show_bug.cgi?id=11377
-- Gerhard, can you please test if it makes your problem go away? (It
won't make the out of memory messages go away, but it should fix the
kernel panic.)
There is still one open report from a user of doing ip=1.2.3.4 on the
kernel command line causing the interface to come up in a nonfunctional
state in 2.6.27 (whereas the same thing worked in 2.6.26), which is
still being bisected.
thanks,
Lennert
--
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