From: Andi Kleen <andi@firstfloor.org>
To: David VomLehn <dvomlehn@cisco.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH][RFC] Check sk_buff states
Date: Wed, 09 Jun 2010 09:14:06 +0200 [thread overview]
Message-ID: <878w6o65kx.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100608003055.GA29405@dvomlehn-lnx2.corp.sa.net> (David VomLehn's message of "Mon\, 7 Jun 2010 17\:30\:55 -0700")
David VomLehn <dvomlehn@cisco.com> writes:
>
> Some of the errors that can be detected are:
> o Double-freeing an skb_buff
slab debugging should already catch that (although at higher cost)
I would say the big question is how many bugs such a new infrastructure
find. Did you find any?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-06-09 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 0:30 [PATCH][RFC] Check sk_buff states David VomLehn
2010-06-08 4:46 ` Mitchell Erblich
2010-06-08 18:28 ` David VomLehn
2010-06-09 7:14 ` Andi Kleen [this message]
2010-06-09 18:07 ` David VomLehn
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=878w6o65kx.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=dvomlehn@cisco.com \
--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