Jose Luis Alarcon Sanchez wrote: > On Fri, 01 Jun 2007 14:29:14 +0530 > Srinivasa Ds <srinivasa@xxxxxxxxxx> wrote: > >> Jose Luis Alarcon Sanchez wrote: >>> Hi Folks. >>> >>> Yesterday i was compiling and installing the 2.6.22-rc2 kernel >>> downloaded from kernel.org ftp site. >>> >>> I don't know if this part of the dmesg command output can be >>> important for the kernel developers: >>> >>> BUG: at mm/slab.c:777 __find_general_cachep() >>> [] show_trace_log_lvl+0x1a/0x30 >>> [] show_trace+0x12/0x20 >>> [] dump_stack+0x16/0x20 >>> [] __kmalloc+0x99/0xc0 >>> [] __kzalloc+0x18/0x50 >>> [] usb_get_configuration+0x86c/0x1040 [usbcore] >>> [] usb_new_device+0x17/0x100 [usbcore] >>> [] hub_thread+0x747/0xbf0 [usbcore] >>> [] kthread+0x42/0x70 >>> [] kernel_thread_helper+0x7/0x10 >>> ======================= >>> >> This is error message tells that, kernel is trying to allocate zero >> bytes through the kmalloc. >> > > Srinivasa, Thanks very much for your answer. > > And how can this "little mistake" be solved?. This problem is seen in almost other subsystems also(like cpusets,drivers(as in this case) etc.) Solving this problem, entirely depends on factors like how that subsystem has been designed, how that subsystem should behave when it ask for 0 bytes from kmalloc. I would suggest you to go through Linux kernel mailing list(lkml) and see there approaches, That may help you a lot. > > Thanks in advance. > > Regards. > > Jose. > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
