[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d



Hi Martin-Éric,

Martin-Éric Racine wrote:

> I'm not sure if it's too early to report on kernel 3.4 or not, but
> here it goes:

Any package uploaded to the archive is open for bug reports. :)

[...]
> ** Kernel log:
> [   29.054891] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> [   29.054909] DR6: ffff0ff0 DR7: 00000400
> [   29.054928] Process mount (pid: 697, ti=f3eee000 task=f4c69c00 task.ti=f3eee000)
> [   29.054944] Stack:
> [   29.054955]  f551f7d8 c10b6cdd f5624138 c10b5104 f5624138 f3eeff20 f3eeff20 c10b5149
> [   29.054998]  f5624198 f5817c00 f5817c80 c10b5362 f5624318 f5624218 f5817c00 00000000
> [   29.055040]  fffffff3 c10a9dd3 00000000 00000000 00000000 0000002e 00000027 f5812090
> [   29.055081] Call Trace:
> [   29.055107]  [<c10b6cdd>] ? destroy_inode+0x1a/0x3e
> [   29.055132]  [<c10b5104>] ? dentry_kill+0x7f/0x8c
> [   29.055157]  [<c10b5149>] ? shrink_dentry_list+0x38/0x62
> [   29.055183]  [<c10b5362>] ? shrink_dcache_sb+0x40/0x51
> [   29.055209]  [<c10a9dd3>] ? do_remount_sb+0x5b/0x11c
> [   29.055236]  [<c10b9acc>] ? do_mount+0x1de/0x5ca
> [   29.055265]  [<c113b3f0>] ? _copy_from_user+0x28/0x47
> [   29.055293]  [<c108b524>] ? memdup_user+0x26/0x43
> [   29.055318]  [<c10b9f21>] ? sys_mount+0x67/0x96
> [   29.055349]  [<c128e6ec>] ? syscall_call+0x7/0xb
> [   29.055364] Code: 85 c0 75 0f ba ee 00 00 00 b8 58 a4 33 c1 e8 87 6e f6 ff 8b 43 1c ff 88 c4 01 00 00 8b 43 10 8d 50 ff 83 fa fd 77 14 85 c0 74 10 <ff> 08 0f 94 c2 84 d2 74 07 31 d2 e8 ee be fa ff 8b 43 14 8d 50 
> [   29.055607] EIP: [<c10b698e>] __destroy_inode+0x56/0x8d SS:ESP 0068:f3eefef0
> [   29.055640] CR2: 00000000ffffb4ff
> [   29.055657] ---[ end trace b7c0a963a9f117a3 ]---

Could you send the full "oops" trace, starting at the first BUG line?
(It should include the text "Not tainted".)  Even better would be full
"dmesg" output from booting and reproducing the bug.

Thanks for catching it,
Jonathan



Reply to: