updatedb.mlocate ends with error message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mlocate
Description: Ubuntu 8.10
Release: 8.10
After a first run of updatedb.mlocate this night, I found the following error message in /var/log/messages this morning.
Oct 26 08:58:30 neon kernel: [60446.296105] updatedb.mloc D c0187063 0 16824 16818
Oct 26 08:58:30 neon kernel: [60446.296110] f3a25d64 00000086 f3a25cec c0187063 f3a25d1c c0187345 00000010 f747bb9c
Oct 26 08:58:30 neon kernel: [60446.296120] c0187063 f3a25d30 f564f110 0000e385 00000000 000000d0 00000000 f38bde00
Oct 26 08:58:30 neon kernel: [60446.296129] c050f080 f67f4000 f3a24000 f564f388 c190bd00 00000000 00000000 c190bd00
Oct 26 08:58:30 neon kernel: [60446.296138] Call Trace:
Oct 26 08:58:30 neon kernel: [60446.296142] [<c0187063>] ? mempool_
Oct 26 08:58:30 neon kernel: [60446.296153] [<c0187345>] ? mempool_
Oct 26 08:58:30 neon kernel: [60446.296159] [<c0187063>] ? mempool_
Oct 26 08:58:30 neon kernel: [60446.296165] [<c037cd1c>] io_schedule+
Oct 26 08:58:30 neon kernel: [60446.296173] [<c0184a85>] sync_page+0x35/0x60
Oct 26 08:58:30 neon kernel: [60446.296181] [<c037d1aa>] __wait_
Oct 26 08:58:30 neon kernel: [60446.296185] [<c0184a50>] ? sync_page+0x0/0x60
Oct 26 08:58:30 neon kernel: [60446.296191] [<c0184612>] __lock_
Oct 26 08:58:30 neon kernel: [60446.296196] [<c0147500>] ? wake_bit_
Oct 26 08:58:30 neon kernel: [60446.296202] [<c0194212>] lock_page+0x22/0x30
Oct 26 08:58:30 neon kernel: [60446.296207] [<c019714a>] do_swap_
Oct 26 08:58:30 neon kernel: [60446.296212] [<c019339e>] ? page_address+
Oct 26 08:58:30 neon kernel: [60446.296218] [<c01976cb>] handle_
Oct 26 08:58:30 neon kernel: [60446.296223] [<c01bac2e>] ? path_to_
Oct 26 08:58:30 neon kernel: [60446.296230] [<c0380c09>] do_page_
Oct 26 08:58:30 neon kernel: [60446.296237] [<c0380890>] ? do_page_
Oct 26 08:58:30 neon kernel: [60446.296242] [<c0254acf>] ? copy_to_
Oct 26 08:58:30 neon kernel: [60446.296250] [<c01b57b9>] ? cp_new_
Oct 26 08:58:30 neon kernel: [60446.296258] [<c02352c4>] ? aa_file_
Oct 26 08:58:30 neon kernel: [60446.296282] [<f89dcd00>] ? jfs_readdir+
Oct 26 08:58:30 neon kernel: [60446.296308] [<c037d3c8>] ? mutex_unlock+
Oct 26 08:58:30 neon kernel: [60446.296313] [<c01bf5b0>] ? vfs_readdir+
Oct 26 08:58:30 neon kernel: [60446.296319] [<c01bf280>] ? filldir64+0x0/0xf0
Oct 26 08:58:30 neon kernel: [60446.296325] [<c01b3578>] ? fput+0x8/0x30
Oct 26 08:58:30 neon kernel: [60446.296330] [<c01bf682>] ? sys_getdents64+
Oct 26 08:58:30 neon kernel: [60446.296335] [<c0380890>] ? do_page_
Oct 26 08:58:30 neon kernel: [60446.296341] [<c037e9d2>] error_code+
Oct 26 08:58:30 neon kernel: [60446.296346] [<c0370000>] ? default_
Oct 26 08:58:30 neon kernel: [60446.296352] =======
mlocate:
Installed: 0.20-2ubuntu1
Candidate: 0.20-2ubuntu1
Version table:
*** 0.20-2ubuntu1 0
500 http://
100 /var/lib/
This crash in fact appears to come from the kernel; updatedb.mlocate was the userspace process running at the time, but in general a reasonably innocuous process like this should not be able to cause the kernel to crash. Reassigning.