Module: xenomai-rpm
Branch: for-upstream
Commit: 90b3e7cf6b5768eca6402fd915aef99cea161751
URL:    
http://git.xenomai.org/?p=xenomai-rpm.git;a=commit;h=90b3e7cf6b5768eca6402fd915aef99cea161751

Author: Philippe Gerum <r...@xenomai.org>
Date:   Tue Oct  5 16:11:42 2010 +0200

nucleus: disable u_mode watchdog for MMU-less

Legacy uClibc-based systems may trigger the scary memory corruption
warning in handle_shadow_exit() because pthread keys are not always
deleted upon application exit there. So the message is wrong, and even
more confusing when people actually have kernel and userland supports
in sync.

In a great move toward sloppiness, we assume that uClibc implies
!CONFIG_MMU in this case, and disable the warning message. At any
rate, the requirement for such warning disappears totally when people
get their kernel / userland support in sync, and/or update uClibc to
fix the pthread key deletion issue. The ABI bump in Xenomai 2.6.x will
make this detection even more obsolete.

---

 ksrc/nucleus/shadow.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/ksrc/nucleus/shadow.c b/ksrc/nucleus/shadow.c
index da03f21..5ac182b 100644
--- a/ksrc/nucleus/shadow.c
+++ b/ksrc/nucleus/shadow.c
@@ -2214,10 +2214,12 @@ static void handle_shadow_exit(void)
         */
        if (thread->u_mode && !warned) {
                warned = 1;
+#ifndef CONFIG_MMU
                printk(KERN_WARNING
                       "Xenomai: User-space support anterior to 2.5.2"
                       " detected, may corrupt memory upon\n"
                       "thread termination. Upgrade is recommended\n");
+#endif
        }
        thread->u_mode = NULL;
 }


_______________________________________________
Xenomai-git mailing list
Xenomai-git@gna.org
https://mail.gna.org/listinfo/xenomai-git

Reply via email to