2.6.32.9 Release notes

it is as none of us made such a claim you're trying to push here, in fact every time this comes up we make a claim to the contrary: kernel devs are not expected to figure out the security impact of bugs because they're not qualified to do so. just look at Jon's effort here and how he missed #1 and mischaracterized #2.

> I'm too lazy to look it up

you're not lazy to look it up, you're unable to but needed a convenient excuse.

> but nearly every time that there is a security problem in a kernel update

you're welcome to find a *single* post from us that makes a claim you wish to attribute to us. after all, if it was 'nearly every time' you won't have to spend more than a few seconds to find one.

> someone belly aches that the kernel developers should figure out for if this bug is a security problem for them.

we never made such a claim, and in fact i don't recall anyone else making it either. but the onus is on you to back up your statement.

> I didn't point anyone out explicitly, but it does appear that I hit a nerve.

considering the amount of trolling and shouting from you, i know whose nerve was hit ;).