[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090430.094614.13889468.davem@davemloft.net>
Date: Thu, 30 Apr 2009 09:46:14 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dvomlehn@...co.com
Cc: netdev@...r.kernel.org
Subject: Re: [Patch 1/1][RFC] NETDEV: Find network bugs by validating the
sk_buff state
From: David VomLehn <dvomlehn@...co.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!
--
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