From: David Miller <davem@davemloft.net>
To: dvomlehn@cisco.com
Cc: netdev@vger.kernel.org
Subject: Re: [Patch 1/1][RFC] NETDEV: Find network bugs by validating the sk_buff state
Date: Thu, 30 Apr 2009 09:46:14 -0700 (PDT) [thread overview]
Message-ID: <20090430.094614.13889468.davem@davemloft.net> (raw)
In-Reply-To: <20090430163200.GC15170@cuplxvomd02.corp.sa.net>
From: David VomLehn <dvomlehn@cisco.com>
Date: Thu, 30 Apr 2009 09:32:00 -0700
> I think the size is very doable. Only two bits are needed to encode
> the state so the ability to check the state isn't an issue. The
> other piece, though, is recording enough information to be able to
> pinpoint the problem.
It's not my job to design this thing for you, but I guess that's what
I have to do to get you to think out of the box a little bit :-/
Maintain a table, which is only recorded into when the debugging
feature is enable (via sysctl or whatever) which remembers this stuff.
That way nobody eats the space or time overhead unless the debugging
feature is enabled.
Wow, I had to use every brain cell I have to come up with that one!
next prev parent reply other threads:[~2009-04-30 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 4:05 [Patch 1/1][RFC] NETDEV: Find network bugs by validating the sk_buff state David VomLehn
2009-04-29 5:30 ` David Miller
2009-04-29 15:14 ` David VomLehn
2009-04-29 21:53 ` David Miller
2009-04-29 22:28 ` David VomLehn
2009-04-29 22:44 ` David Miller
2009-04-30 16:32 ` David VomLehn
2009-04-30 16:46 ` David Miller [this message]
2009-04-30 17:59 ` David VomLehn
2009-04-30 18:05 ` David Miller
2009-04-30 18:23 ` 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=20090430.094614.13889468.davem@davemloft.net \
--to=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).