From: David Miller <davem@davemloft.net>
To: n0-1@freewrt.org
Cc: netdev@vger.kernel.org, akpm@linux-foundation.org,
florian@openwrt.org, roel.kluin@gmail.com
Subject: Re: [PATCH 2/2] korina: add error-handling to korina_alloc_ring
Date: Thu, 13 Aug 2009 16:27:43 -0700 (PDT) [thread overview]
Message-ID: <20090813.162743.29979567.davem@davemloft.net> (raw)
In-Reply-To: <20090812225234.82E6E4CEAA@orbit.nwl.cc>
From: Phil Sutter <n0-1@freewrt.org>
Date: Thu, 13 Aug 2009 00:52:32 +0200
> This also avoids a potential buffer overflow in case the very first
> receive descriptor fails to allocate, as an index of -1 would be used
> afterwards. Kudos to Roel Kluin for pointing this out and providing an
> initial patch.
>
> Signed-off-by: Phil Sutter <n0-1@freewrt.org>
Applied to net-next-2.6
next prev parent reply other threads:[~2009-08-13 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 15:33 [PATCH] korina: Read buffer overflow Roel Kluin
2009-08-08 0:48 ` Phil Sutter
2009-08-08 13:14 ` roel kluin
2009-08-08 16:45 ` Phil Sutter
2009-08-09 0:06 ` Phil Sutter
2009-08-12 22:15 ` Phil Sutter
2009-08-12 22:22 ` [PATCH 1/2] korina: fix printk formatting, add final info line Phil Sutter
2009-08-12 22:52 ` [PATCH 2/2] korina: add error-handling to korina_alloc_ring Phil Sutter
2009-08-13 23:27 ` David Miller [this message]
2009-08-13 23:27 ` [PATCH 1/2] korina: fix printk formatting, add final info line David Miller
[not found] ` <1249776388-4626-1-git-send-email-n0-1@freewrt.org>
2009-08-09 0:06 ` [PATCH 1/3] " Phil Sutter
[not found] ` <1249776388-4626-2-git-send-email-n0-1@freewrt.org>
2009-08-09 0:06 ` [PATCH 2/3] korina: add error-handling to korina_alloc_ring Phil Sutter
[not found] ` <1249776388-4626-3-git-send-email-n0-1@freewrt.org>
2009-08-09 0:06 ` [PATCH 3/3] korina: convert to net_device_ops Phil Sutter
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=20090813.162743.29979567.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=florian@openwrt.org \
--cc=n0-1@freewrt.org \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@gmail.com \
/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).