From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Soetens Date: Mon, 17 Sep 2007 14:55:49 +0200 References: <200709071127.17913.peter.soetens@domain.hid> <1189882379.25006.181.camel@domain.hid> In-Reply-To: <1189882379.25006.181.camel@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709171455.49748.peter.soetens@domain.hid> Subject: Re: [Xenomai-core] [FIX] Summary: Xenomai 2.3.2 and 2.4 lock-ups and OOPSes List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai-core On Saturday 15 September 2007 20:52:59 Philippe Gerum wrote: > On Fri, 2007-09-07 at 11:27 +0200, Peter Soetens wrote: > > Just in case you hooked off the long discussion about the issues we found > > from Xenomai 2.3.2 on: > > > > o We are using the xeno_native skin, create Xeno tasks and semaphores, > > but have strong indications that the crashes are caused by the memory > > allocation scheme of Xenomai in combination with task creation/deletion > > o We found two ways to break Xenomai, causing a 'Killed' > > (rt_task_delete) and causing an OOPS (rt_task_join). > > o They happen on 2.6.20 and 2.6.22 kernels > > o On the 2.3 branch, r2429 works, r2433 causes the faults. The patch is > > small, and in the ChangLog: > > Please try this patch against v2.3.x. A double free issue on a task TCB > already scheduled for memory release was causing all sorts of troubles, > basically trashing the system heap afterwards: Thanks, we'll try, test and report ASAP (= somewhere this week.) Peter -- Peter Soetens -- FMTC --