On 06/21/2011 02:49 PM, Eric W. Biederman wrote:
<snip>
I respectfully suggest that the bug is elsewhere perhaps a broken user
space application out there that needs to be fixed, or you have a kernel
memory stomp that removing patch a05d2ad happens to shift the memory
layout to be harmful in a different way.
OK, I'm remembering how PF_UNIX Unix domain sockets are used, so I think
your theory about a misbehaving user space application is more likely.
However, I am a bit confused about how an application can attempt to
receive before the socket is fully opened. Some kind of race condition
with socketpair() ?
rtg
--
Tim Gardner tim.gardner@canonical.com