Hello,

using:
- vanilla kernel 2.6.28.7.
- aufs 2-standalone.tree-28-20090914

calling "lsof" causes the following oops:

-------------------- snip ----------------------------------
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] ------------[ cut 
here ]------------
Sep 25 18:41:04 I686EMG user.crit kernel: [   58.952453] kernel BUG at 
fs/aufs/i_op.c:711!
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] invalid opcode: 0000 
[#1]
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] last sysfs 
file: /sys/devices/virtual/net/ippp2/address
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] Modules linked in: 
deflate zlib_deflate zlib_inflate twofish twofish_common serpent blowfish ecb 
xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 des_generic md5 
sha1_generic af_key xt_policy xt_tcpudp
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453]
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] Pid: 2406, comm: lsof 
Not tainted (2.6.28.7 #1) 945GS
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] EIP: 0060:
[<f831a684>] EFLAGS: 00010216 CPU: 0
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] EIP is at 
aufs_getattr+0x113/0x3e2 [aufs]
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] EAX: f6d81280 EBX: 
00000002 ECX: f6d7bf20 EDX: f6d7bf20
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453] ESI: f6d80074 EDI: 
f700ce40 EBP: f6d7bdac ESP: f6911efc
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453]  DS: 007b ES: 007b 
FS: 0000 GS: 0033 SS: 0068
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] Process lsof (pid: 
2406, ti=f6910000 task=f70db4c0 task.ti=f6910000)
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] Stack:
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.952453]  f6911f64 f6d7bf20 
00001049 00000000 f6810400 00000001 f6d7b9cc f700ce40
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  c01540ae 00000001 
f6911f48 f831a571 f6d7bf20 f700ce40 f6910000 c014b436
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  00000000 f6911f64 
f6911f4c c014b8a7 f700ce40 f6d7bf20 08064220 ffffffc8
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] Call Trace:
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c01540ae>] 
__d_path+0xc1/0x106
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<f831a571>] 
aufs_getattr+0x0/0x3e2 [aufs]
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c014b436>] 
vfs_getattr+0x21/0x30
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c014b8a7>] 
vfs_stat_fd+0x2a/0x3b
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c014b945>] 
sys_stat64+0xf/0x23
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c0171151>] 
proc_pid_readlink+0x9a/0xa4
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c01549cf>] 
dput+0x44/0xf3
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c0157c8d>] 
mntput_no_expire+0x13/0x82
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c014b7ce>] 
sys_readlinkat+0x6d/0x74
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c014b7e8>] 
sys_readlink+0x13/0x17
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c0102ae1>] 
sysenter_do_call+0x12/0x25
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453]  [<c0280000>] 
unix_stream_recvmsg+0x3b7/0x3d6
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] Code: 8b 54 24 04 8b 
42 50 39 18 75 15 8d 46 d4 31 d2 83 78 24 00 74 02 89 c2 39 1a 0f 84 ca 00 00 
00 8b 4c 24 04 8b 69 14 39 e9 74 04 <0f> 0b eb fe 8b 44 24 04 31 d2 8b 40 08 
89 44 24 14 8b 44 24 04
Sep 25 18:41:04 I686EMG user.emerg kernel: [   58.952453] EIP: [<f831a684>] 
aufs_getattr+0x113/0x3e2 [aufs] SS:ESP 0068:f6911efc
Sep 25 18:41:04 I686EMG user.warn kernel: [   58.962861] ---[ end trace 
15759a5f2ef34516 ]---
-------------------- snap ----------------------------------

Has anyone an idea where to start? What additional informations are needed?

Siegfried

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf

Reply via email to