From: Jeff Garzik <jeff@garzik.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: netdev@vger.kernel.org, Dale Farnsworth <dale@farnsworth.org>,
Nicolas Pitre <nico@cam.org>, Andrew Morton <akpm@osdl.org>,
Gerhard Bertelsmann <info@gerhard-bertelsmann.de>
Subject: Re: mv643xx_eth fixes pull request for 2.6.27
Date: Wed, 27 Aug 2008 05:10:45 -0400 [thread overview]
Message-ID: <48B51A15.5080801@garzik.org> (raw)
In-Reply-To: <20080825203139.GA18649@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Sun, Aug 24, 2008 at 04:03:24AM +0200, Lennert Buytenhek wrote:
>
>> 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.)
>
> The submitter confirmed that patch 2 fixes the original issue (and
> once that is fixed, patch 4 will fix the subsequently emerging issue).
> I've also done some more testing on the series, and it's probably good
> for 2.6.27. I've tacked on a patch to bump the version number -- can
> you please pull?
>
> The following changes 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=shortlog;h=for-2.6.27
>
> Lennert Buytenhek (6):
> 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
> mv643xx_eth: bump version to 1.3
>
> drivers/net/mv643xx_eth.c | 35 ++++++++++++++++++++---------------
> 1 files changed, 20 insertions(+), 15 deletions(-)
pulled
prev parent reply other threads:[~2008-08-27 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 2:03 [PATCH 0/5,RFC] mv643xx_eth fixes for 2.6.27 Lennert Buytenhek
2008-08-25 20:31 ` mv643xx_eth fixes pull request for 2.6.27 (was: Re: [PATCH 0/5,RFC] mv643xx_eth fixes for 2.6.27) Lennert Buytenhek
2008-08-27 9:10 ` Jeff Garzik [this message]
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=48B51A15.5080801@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=buytenh@wantstofly.org \
--cc=dale@farnsworth.org \
--cc=info@gerhard-bertelsmann.de \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.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).