Bug 72345 - kpilotDaemon calendar/todo conduit memory leak and crash
Summary: kpilotDaemon calendar/todo conduit memory leak and crash
Status: RESOLVED DUPLICATE of bug 72226
Alias: None
Product: kpilot
Classification: Applications
Component: Calendar Conduit (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Reinhold Kainhofer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-11 00:26 UTC by drac
Modified: 2004-01-11 09:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description drac 2004-01-11 00:26:58 UTC 
Version:           4.4.0 (HEAD) (using KDE 3.1.94 (CVS >= 20031206), SuSE)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:          Linux (i686) release 2.6.0-1-default

kpilotDaemon crashes and consumes all available memory when syncing todo list. I created new empty calendar file for testing and result is also same. I am able to successfully sync all other items (calendar, notes, etc) when I disable todo conduit.

Here's dmesg output:

visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB
0
Unable to handle kernel NULL pointer dereference at virtual address 00000024
 printing eip:
c016b91d
*pde = 00000000
Oops: 0000 [#7]
CPU:    0
EIP:    0060:[<c016b91d>]    Tainted: PF
EFLAGS: 00010202
EIP is at simple_rmdir+0x1d/0x40
eax: 00000000   ebx: e292ce80   ecx: e292ce80   edx: ffffffd9
esi: eef48800   edi: e292ce9c   ebp: 00000000   esp: e3e03d78
ds: 007b   es: 007b   ss: 0068
Process kpilotDaemon (pid: 15817, threadinfo=e3e02000 task=edfdc080)
Stack: e292c880 e292ce80 c01847dc eef48800 e292ce80 ea9fa980 d7b01a80 e292ce80
       c01848c9 e292ce80 e85074a0 d9e5d194 d0855300 c01c1d28 e85074a0 e8507478
       c0207a41 e85074a0 e8507478 f0b5b6f4 e8507478 00000000 c0207a8b e8507478
Call Trace:
 [<c01847dc>] remove_dir+0x3c/0x60
 [<c01848c9>] sysfs_remove_dir+0xb9/0xd0
 [<c01c1d28>] kobject_del+0x68/0x80
 [<c0207a41>] device_del+0x61/0xa0
 [<c0207a8b>] device_unregister+0xb/0x20
 [<f0b55ed0>] destroy_serial+0x70/0x170 [usbserial]
 [<c01c1e09>] kobject_cleanup+0x69/0x70
 [<c01efc4a>] release_dev+0x2ca/0x570
 [<c011c711>] __wake_up+0x11/0x20
 [<c0152c3c>] invalidate_inode_buffers+0xc/0x50
 [<c016610d>] destroy_inode+0x3d/0x50
 [<c01f024a>] tty_release+0xa/0x10
 [<c0151cc8>] __fput+0xb8/0xf0
 [<c0150843>] filp_close+0x43/0x70
 [<c01204dd>] put_files_struct+0x4d/0xb0
 [<c012107a>] do_exit+0x14a/0x300
 [<c01212bb>] do_group_exit+0x2b/0x70
 [<c0128fc9>] get_signal_to_deliver+0x209/0x2f0
 [<c010ad09>] do_signal+0x49/0xf0
 [<c011b70c>] recalc_task_prio+0x9c/0x200
 [<c011c2e4>] schedule+0x1c4/0x570
 [<c0119c90>] do_page_fault+0x0/0x500
 [<c010ade7>] do_notify_resume+0x37/0x40
 [<c010afce>] work_notifysig+0x13/0x15

Code: 8b 50 24 4a 89 50 24 53 56 e8 b5 ff ff ff 8b 46 24 31 d2 48
Comment 1 Reinhold Kainhofer 2004-01-11 09:44:36 UTC 
I can confirm this. Strangely it only happens with the todo conduit, not with the calendar conduit (which is basically the same code base). 

*** This bug has been marked as a duplicate of 72226 ***