Re: [PATCH] getsockopt() early argument sanity checking

> We're not assuming they're broken. When some code is maintained by many people
> and when conventions differ between similar functions (eg: setsockopt does
> the check at top level and getsockopt in the leaves),

thats not something you want to fix in 2.4 though ;)

it may be worth considering for 2.6 of course.

-
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: [PATCH] getsockopt() early argument sanity checking
  - From: Willy Tarreau <[email protected]>
- Re: [PATCH] getsockopt() early argument sanity checking
  - From: Michael Buesch <[email protected]>
- Re: [PATCH] getsockopt() early argument sanity checking
  - From: Willy Tarreau <[email protected]>
- Re: [PATCH] getsockopt() early argument sanity checking
  - From: David Miller <[email protected]>
- Re: [PATCH] getsockopt() early argument sanity checking
  - From: Willy Tarreau <[email protected]>

Prev by Date: Re: PROBLEM: FUSE unmount breaks serial terminal line
Next by Date: Re: [PATCH] 2.6.17.9 Incorrect string length checking in param_set_copystring()
Previous by thread: Re: [PATCH] getsockopt() early argument sanity checking
Next by thread: Re: [PATCH] getsockopt() early argument sanity checking
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]