From mboxrd@z Thu Jan 1 00:00:00 1970 From: morfeas3000@gmail.com (NorthPole) Date: Fri, 22 Jun 2012 03:50:49 +0300 Subject: geting weird semi-random panic on kmalloc Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Hello everyone I'm making my first steps in the linux kernel developpement by trying to add some functionality in a kernel module I have a problem that I cant seem to grasp and would greatly appreciate any help. I have this piece of code: http://pastebin.com/igP7255S which is called by this: for(i=0;i<250;i++) registerTvlv(i,0x01,1,&batadv_ogm_packet->gw_flags,bat_priv,batadv_ogm_packet); This is supposed to add 250 distinct tlvs in the list batadv_ogm_packet->gw_flags is used both above and bellow the invocation and the module doesnt crash the same stands for these two bat_priv and batadv_ogm_packet when I run the kernel code on an open-wrt build for x86 which is run virtualized under a standard qemu running on debian squeeze produces this output http://pastebin.com/tY3Vkzvw (in short it prints everything as its supposed to do for a random number of iterations between 3 and 24 and the the kernel oops happens) But i cant understand why the problem seems to happen at the kmalloc line (havent figured how to use gdb for open wrt kernel debugging yet so i'm relying on printk for debugging) the qemu instance loads with these setings screen qemu\ -no-acpi -m 128M \ -net vde,sock=num1.ctl,port=1 -net nic,macaddr=fe:fe:00:00:01:01 \ -net nic -net tap,ifname=tapwrt1,script=no,downscript=no \ -nographic \ num1.image Thank you for your time and answers Spyros -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120622/995f127e/attachment.html