Re: IPv4: ip_options_compile() how can we avoid blowing up on a NULL skb???

Dmitry Torokhov <[email protected]> wrote:
> 
> BUG()s there would be a mechanism to document invariants so next time
> someone is looking at the code there are no questions.

Well if someone is documenting this then wouldn't a comment (or even a
kerneldoc style block) be better?

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Re: IPv4: ip_options_compile() how can we avoid blowing up on a NULL skb???
  - From: Dmitry Torokhov <[email protected]>

Prev by Date: Re: [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled
Next by Date: [PATCH] visws: sgivwfb is module needs exports
Previous by thread: Re: IPv4: ip_options_compile() how can we avoid blowing up on a NULL skb???
Next by thread: Re: IPv4: ip_options_compile() how can we avoid blowing up on a NULL skb???
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]