On Fri, 2007-02-02 at 10:33 +0100, Philippe Gerum wrote: > On Fri, 2007-02-02 at 09:43 +0100, M. Koehrer wrote: > > Hi everybody, > > > > I have a strange issue frequently when reading /proc/xenomai/stat. > > I do a cat /proc/xenomai/stat and I get an "Cannot allocate memory" error. > > This happens typcially after I have started and terminated by application > > that uses a number of tasks. > > I am able to reproduce it deterministically... > > While the application is running, I can see the stat values perfectly. > > Here is the head output of all /proc/xenomai/* files: > > At first sight looking at the code, there seems to be a memory leak > caused by an unfree kmalloc() block in the sched & stat sequence > routines. Will confirm and fix. Thanks, >
Not confirmed for the leakage part regarding kmalloc(). We do have a seq_release_private() freeing the allocated block, so back to square #1. This said, some kernel memory is not released somewhere, as running vmstat tells me here. Btw, is the rest of your system functional after the error occurs, or is a reboot needed afterwise? -- Philippe. _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
