Olaf Kirch wrote:
> On Wednesday 25 April 2007 23:03, Vlad Yasevich wrote:
>> It looks like someone is stepping all over the inet_sock.
>> We'll continue looking, but if anyone has any ideas of what might
>> be going on, I'd appreciate it.
>
> This could be a socket in TIME_WAIT. A socket entering
On 4/26/07, Olaf Kirch <[EMAIL PROTECTED]> wrote:
On Wednesday 25 April 2007 23:03, Vlad Yasevich wrote:
> It looks like someone is stepping all over the inet_sock.
> We'll continue looking, but if anyone has any ideas of what might
> be going on, I'd appreciate it.
This could be a socket in TIM
Sridhar Samudrala wrote:
>> The corruption is triggered after about 10 minutes of running the following
>> script:
>>
>> nfspath = $1
>> localpath = $2
>> while true; do
>> mount "$nfspath" "$localpath"
>> sleep 5
>> cp /boot/vmlinuz "$localpath"
>> sleep 5
>> rm $localpath
On Wednesday 25 April 2007 23:03, Vlad Yasevich wrote:
> It looks like someone is stepping all over the inet_sock.
> We'll continue looking, but if anyone has any ideas of what might
> be going on, I'd appreciate it.
This could be a socket in TIME_WAIT. A socket entering
TIME_WAIT will be replaced
On Wed, 2007-04-25 at 17:03 -0400, Vlad Yasevich wrote:
> Hi All
>
> To support a piece of custom functionality, we needed to add
> 2 member to the struct inet_sock. During testing, we started
> seeing an interesting corruption. Following a hunch, we've
> completely ripped out all of our code wi
Hi All
To support a piece of custom functionality, we needed to add
2 member to the struct inet_sock. During testing, we started
seeing an interesting corruption. Following a hunch, we've
completely ripped out all of our code with the exception of
5 lines that do this:
diff --git a/include/net/
