oops in VMWARE vmnet, on 2.6.12.x

oops in VMWARE vmnet, on 2.6.12.x

[Grzegorz Piotr Jaskiewicz]

I know that in general no one here is interested in vmware affairs, but in 
hope that VMware folks are reading this list too, here's the oops:
It's the newest vmware5 for linux from vmware.com

ksymoops 2.4.9 on i686 2.6.12.4.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.6.12.4/ (default)
     -m /boot/System.map-2.6.12.4 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
c02993d7
*pde = 00000000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c02993d7>]    Tainted: P      VLI
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282   (2.6.12.4)
eax: 00000001   ebx: d559e800   ecx: 0000000b   edx: df307800
esi: d559e80c   edi: 00000000   ebp: d1a4fdf0   esp: d1a4fdd0
ds: 007b   es: 007b   ss: 0068
Stack: 00000000 df307800 ffffffff 0000000a df307934 d559e800 d559e80c 00000000
       d1a4fe14 e1a31707 00000010 00000020 00000001 00000000 d559e800 df307805
       d559e811 d1a4fe3c e1a3187a d559e800 d559e80c d1a4fe34 c01381a6 d559e80c
Call Trace:
 [<c0103c2b>] show_stack+0x80/0x96
 [<c0103dbb>] show_registers+0x15a/0x1d1
 [<c0103fa7>] die+0xd2/0x14b
 [<c0115c8f>] do_page_fault+0x455/0x68e
 [<c01038a3>] error_code+0x4f/0x54
 [<e1a31707>] VNetBridgeUp+0xe5/0x16b [vmnet]
 [<e1a3187a>] VNetBridgeNotify+0x7e/0x167 [vmnet]
 [<c029fb49>] register_netdevice_notifier+0x6f/0x74
 [<e1a3104c>] VNetBridge_Create+0x88/0x279 [vmnet]
 [<e1a2e67c>] VNetFileOpIoctl+0x24a/0x4d3 [vmnet]
 [<c0164657>] do_ioctl+0x4f/0x74
 [<c01647bc>] vfs_ioctl+0x62/0x1c2
 [<c0164993>] sys_ioctl+0x77/0x84
 [<c0102d81>] syscall_call+0x7/0xb
Code: e9 39 fc ff ff ba ea ff ff ff c7 85 68 ff ff ff 04 00 00 00 e9 fd fb ff 
ff 55 89 e5 83 ec 20 8b 45 10 89 5d f4 89 75 f8 89 7d fc <8b> 70 68 85 f6 0f 
84 02 01 00 00 8b 55 0c 89 34 24 89 54 24 04


>>EIP; c02993d7 <sk_alloc+12/150>   <=====

>>ebx; d559e800 <pg0+1516c800/3fbcc400>
>>edx; df307800 <pg0+1eed5800/3fbcc400>
>>esi; d559e80c <pg0+1516c80c/3fbcc400>
>>ebp; d1a4fdf0 <pg0+1161ddf0/3fbcc400>
>>esp; d1a4fdd0 <pg0+1161ddd0/3fbcc400>

Trace; c0103c2b <show_stack+80/96>
Trace; c0103dbb <show_registers+15a/1d1>
Trace; c0103fa7 <die+d2/14b>
Trace; c0115c8f <do_page_fault+455/68e>
Trace; c01038a3 <error_code+4f/54>
Trace; e1a31707 <pg0+215ff707/3fbcc400>
Trace; e1a3187a <pg0+215ff87a/3fbcc400>
Trace; c029fb49 <register_netdevice_notifier+6f/74>
Trace; e1a3104c <pg0+215ff04c/3fbcc400>
Trace; e1a2e67c <pg0+215fc67c/3fbcc400>
Trace; c0164657 <do_ioctl+4f/74>
Trace; c01647bc <vfs_ioctl+62/1c2>
Trace; c0164993 <sys_ioctl+77/84>
Trace; c0102d81 <syscall_call+7/b>

This architecture has variable length instructions, decoding before eip
is unreliable, take these instructions with a pinch of salt.

Code;  c02993ac <sock_getsockopt+43d/456>
00000000 <_EIP>:
Code;  c02993ac <sock_getsockopt+43d/456>
   0:   e9 39 fc ff ff            jmp    fffffc3e <_EIP+0xfffffc3e>
Code;  c02993b1 <sock_getsockopt+442/456>
   5:   ba ea ff ff ff            mov    $0xffffffea,%edx
Code;  c02993b6 <sock_getsockopt+447/456>
   a:   c7 85 68 ff ff ff 04      movl   $0x4,0xffffff68(%ebp)
Code;  c02993bd <sock_getsockopt+44e/456>
  11:   00 00 00
Code;  c02993c0 <sock_getsockopt+451/456>
  14:   e9 fd fb ff ff            jmp    fffffc16 <_EIP+0xfffffc16>
Code;  c02993c5 <sk_alloc+0/150>
  19:   55                        push   %ebp
Code;  c02993c6 <sk_alloc+1/150>
  1a:   89 e5                     mov    %esp,%ebp
Code;  c02993c8 <sk_alloc+3/150>
  1c:   83 ec 20                  sub    $0x20,%esp
Code;  c02993cb <sk_alloc+6/150>
  1f:   8b 45 10                  mov    0x10(%ebp),%eax
Code;  c02993ce <sk_alloc+9/150>
  22:   89 5d f4                  mov    %ebx,0xfffffff4(%ebp)
Code;  c02993d1 <sk_alloc+c/150>
  25:   89 75 f8                  mov    %esi,0xfffffff8(%ebp)
Code;  c02993d4 <sk_alloc+f/150>
  28:   89 7d fc                  mov    %edi,0xfffffffc(%ebp)

This decode from eip onwards should be reliable

Code;  c02993d7 <sk_alloc+12/150>
00000000 <_EIP>:
Code;  c02993d7 <sk_alloc+12/150>   <=====
   0:   8b 70 68                  mov    0x68(%eax),%esi   <=====
Code;  c02993da <sk_alloc+15/150>
   3:   85 f6                     test   %esi,%esi
Code;  c02993dc <sk_alloc+17/150>
   5:   0f 84 02 01 00 00         je     10d <_EIP+0x10d>
Code;  c02993e2 <sk_alloc+1d/150>
   b:   8b 55 0c                  mov    0xc(%ebp),%edx
Code;  c02993e5 <sk_alloc+20/150>
   e:   89 34 24                  mov    %esi,(%esp)
Code;  c02993e8 <sk_alloc+23/150>
  11:   89 54 24 04               mov    %edx,0x4(%esp)


Thanks.

-- 
GJ

Binary system, you're either 1 or 0...
dead or alive ;)

Re: oops in VMWARE vmnet, on 2.6.12.x

[Lee Revell]

On Tue, 2005-08-09 at 17:44 +0200, Grzegorz Piotr Jaskiewicz wrote:
> I know that in general no one here is interested in vmware affairs, but in 
> hope that VMware folks are reading this list too, here's the oops:
> It's the newest vmware5 for linux from vmware.com
> 
> ksymoops 2.4.9 on i686 2.6.12.4.

Don't use ksymoops on 2.6.

Lee

Re: oops in VMWARE vmnet, on 2.6.12.x

[Andreas Steinmetz]

Grzegorz Piotr Jaskiewicz wrote:
> I know that in general no one here is interested in vmware affairs, but in 
> hope that VMware folks are reading this list too, here's the oops:
> It's the newest vmware5 for linux from vmware.com

ftp://platan.vc.cvut.cz/pub/vmware/vmware-any-any-update93.tar.gz

-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

Re: oops in VMWARE vmnet, on 2.6.12.x

[Petr Vandrovec]

Grzegorz Piotr Jaskiewicz wrote:
> I know that in general no one here is interested in vmware affairs, but in 
> hope that VMware folks are reading this list too, here's the oops:
> It's the newest vmware5 for linux from vmware.com

You must update vmnet with vmware-any-any-update93 patch
(http://platan.vc.cvut.cz/ftp/pub/vmware).  sk_alloc() function
changed type of its arguments, and unfortunately this causes only
compile-time warning, which you did not notice, but resulting module crashes
kernel as now mandatory argument is passed in as '0'.

You should report problems related to the VMware at the VMware community forums,
http://www.vmware.com/community/index.jspa.  Most of peoples on LKML does not
care about these opensource modules.
								Petr Vandrovec

Re: oops in VMWARE vmnet, on 2.6.12.x

[Christoph Hellwig]

On Tue, Aug 09, 2005 at 05:56:45PM +0200, Petr Vandrovec wrote:
> You should report problems related to the VMware at the VMware community 
> forums,
> http://www.vmware.com/community/index.jspa.  Most of peoples on LKML does 
> not
> care about these opensource modules.

Nothing in the tarball mentiones any opensource license.  If vmware is
actually using an opensource license please tell them to mention that
license and remove the propritary code markers.

Re: oops in VMWARE vmnet, on 2.6.12.x

[Jan Engelhardt]

>Nothing in the tarball mentiones any opensource license.  If vmware is
>actually using an opensource license please tell them to mention that
>license and remove the propritary code markers.

It's not opensource, but "proprietary and S_IRUGO". Though, the world won't 
fall down instantly if you change something [e.g. bugfix] and redistribute 
(with all the copyright stuff intact, and for non-profit)

Re: oops in VMWARE vmnet, on 2.6.12.x

[Christoph Hellwig]

On Thu, Aug 11, 2005 at 08:17:28AM +0200, Jan Engelhardt wrote:
> 
> >Nothing in the tarball mentiones any opensource license.  If vmware is

please read this sentence again.  Just because somethings source is available
doesn't mean it's opensource.

> >actually using an opensource license please tell them to mention that
> >license and remove the propritary code markers.
> 
> It's not opensource, but "proprietary and S_IRUGO". Though, the world won't 
> fall down instantly if you change something [e.g. bugfix] and redistribute 
> (with all the copyright stuff intact, and for non-profit)

Re: oops in VMWARE vmnet, on 2.6.12.x

[linux-os (Dick Johnson)]

On Tue, 6 Sep 2005, Christoph Hellwig wrote:

> On Thu, Aug 11, 2005 at 08:17:28AM +0200, Jan Engelhardt wrote:
>>
>>> Nothing in the tarball mentiones any opensource license.  If vmware is
>
> please read this sentence again.  Just because somethings source is available
> doesn't mean it's opensource.
>

Sure it is! It just isn't the GNU flavor of open source. It's likely
that it's even "compatible" as long as it's not more restrictive
than GNU.

Often the "GNU protestants" are rejecting perfectly good work because
they have adopted a highly restrictive religion, having been taught
that it is the true meaning of freedom. Marx would be so proud!

Wonderful thing about published private works, i.e., proprietary
source-code, is that you can use it as a reference and write your
own version(s). Since it's published, you don't need "clean-room"
techniques. You just can't grab portions "whole cloth" and paste
them into your source.

When your driver, probably with improvements, is finished it
is normal, but not necessary to provide some attribution in the
source such as "Adapted from xxx.yyy.zzz" as a public "thank you".

>>> actually using an opensource license please tell them to mention that
>>> license and remove the propritary code markers.
>>
>> It's not opensource, but "proprietary and S_IRUGO". Though, the world won't
>> fall down instantly if you change something [e.g. bugfix] and redistribute
>> (with all the copyright stuff intact, and for non-profit)
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
Warning : 98.36% of all statistics are fiction.
.
I apologize for the following. I tried to kill it with the above dot :

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: oops in VMWARE vmnet, on 2.6.12.x

[Mathieu]

"linux-os \(Dick Johnson\)" <linux-os@analogic.com> disait dernièrement que :

are you serious or just on drugs ?

> On Tue, 6 Sep 2005, Christoph Hellwig wrote:
>
>> On Thu, Aug 11, 2005 at 08:17:28AM +0200, Jan Engelhardt wrote:
>>>
>>>> Nothing in the tarball mentiones any opensource license.  If vmware is
>>
>> please read this sentence again.  Just because somethings source is available
>> doesn't mean it's opensource.
>>
>
> Sure it is! It just isn't the GNU flavor of open source. It's likely
> that it's even "compatible" as long as it's not more restrictive
> than GNU.
>
> Often the "GNU protestants" are rejecting perfectly good work because
> they have adopted a highly restrictive religion, having been taught
> that it is the true meaning of freedom. Marx would be so proud!
>
> Wonderful thing about published private works, i.e., proprietary
> source-code, is that you can use it as a reference and write your
> own version(s). Since it's published, you don't need "clean-room"
> techniques. You just can't grab portions "whole cloth" and paste
> them into your source.
>
> When your driver, probably with improvements, is finished it
> is normal, but not necessary to provide some attribution in the
> source such as "Adapted from xxx.yyy.zzz" as a public "thank you".
>
>>>> actually using an opensource license please tell them to mention that
>>>> license and remove the propritary code markers.
>>>
>>> It's not opensource, but "proprietary and S_IRUGO". Though, the world won't
>>> fall down instantly if you change something [e.g. bugfix] and redistribute
>>> (with all the copyright stuff intact, and for non-profit)
>>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
> Warning : 98.36% of all statistics are fiction.
> .
> I apologize for the following. I tried to kill it with the above dot :
>
> ****************************************************************
> The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
> Thank you.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

-- 
No fortunes found

Re: oops in VMWARE vmnet, on 2.6.12.x

[linux-os (Dick Johnson)]

On Tue, 6 Sep 2005, Mathieu wrote:

> "linux-os \(Dick Johnson\)" <linux-os@analogic.com> disait dernièrement que :
>
> are you serious or just on drugs ?
>

Absolutely serious although I did try something new this weekend!

>> On Tue, 6 Sep 2005, Christoph Hellwig wrote:
>>
>>> On Thu, Aug 11, 2005 at 08:17:28AM +0200, Jan Engelhardt wrote:
>>>>
>>>>> Nothing in the tarball mentiones any opensource license.  If vmware is
>>>
>>> please read this sentence again.  Just because somethings source is available
>>> doesn't mean it's opensource.
>>>
>>
>> Sure it is! It just isn't the GNU flavor of open source. It's likely
>> that it's even "compatible" as long as it's not more restrictive
>> than GNU.
>>
>> Often the "GNU protestants" are rejecting perfectly good work because
>> they have adopted a highly restrictive religion, having been taught
>> that it is the true meaning of freedom. Marx would be so proud!
>>
>> Wonderful thing about published private works, i.e., proprietary
>> source-code, is that you can use it as a reference and write your
>> own version(s). Since it's published, you don't need "clean-room"
>> techniques. You just can't grab portions "whole cloth" and paste
>> them into your source.
>>
>> When your driver, probably with improvements, is finished it
>> is normal, but not necessary to provide some attribution in the
>> source such as "Adapted from xxx.yyy.zzz" as a public "thank you".
>>
>>>>> actually using an opensource license please tell them to mention that
>>>>> license and remove the propritary code markers.
>>>>
>>>> It's not opensource, but "proprietary and S_IRUGO". Though, the world won't
>>>> fall down instantly if you change something [e.g. bugfix] and redistribute
>>>> (with all the copyright stuff intact, and for non-profit)
>>>
>>
>> Cheers,
>> Dick Johnson
>> Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
>> Warning : 98.36% of all statistics are fiction.
>> .
>> I apologize for the following. I tried to kill it with the above dot :
>>
>> ****************************************************************
>> The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>>
>> Thank you.
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>
>
> --
> No fortunes found
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
Warning : 98.36% of all statistics are fiction.

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: oops in VMWARE vmnet, on 2.6.12.x

[Grzegorz Piotr Jaskiewicz]

On Tuesday 06 September 2005 14:21, Mathieu wrote:
> "linux-os \(Dick Johnson\)" <linux-os@analogic.com> disait dernièrement que
> :
>
> are you serious or just on drugs ?
Someone was on drugs in first place, when he decided to change API in such 
baaad way.....


-- 
GJ

Binary system, you're either 1 or 0...
dead or alive ;)