From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Bug with Xenomai and xeno_heap: Eeek! page_mapcount(page) went negative!
Date: Fri, 10 Oct 2008 11:06:31 +0200 [thread overview]
Message-ID: <48EF1B17.807@domain.hid> (raw)
In-Reply-To: <8227750.1223626784795.JavaMail.ngmail@domain.hid>
M. Koehrer wrote:
> Hello Gilles,
>
> I tried a couple of Xenomai/Kernel combinations.
> The result is the following:
>
> Xeno 2.4.4 and kernel 2.6.25: ok
> Xeno 2.4.5 and kernel 2.6.25: ok
> Xeno 2.4.5 and kernel 2.6.26: crash
> (In all tests, I used the adeos patch that was part of the release Xenomai version).
>
> Thus, some rmap code in kernel 2.6.26 seems to be different than with 2.6.25.
>
> I hope that helps to find out what is wrong...
Yes, thanks. This is a bug which should have been fixed since then. But
here is a patch for your version. Could you try it?
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 816cf71..568cd8d 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -109,7 +109,7 @@ extern unsigned int kobjsize(const void *objp);
#define VM_CAN_NONLINEAR 0x08000000 /* Has ->fault & does nonlinear pages */
#define VM_MIXEDMAP 0x10000000 /* Can contain "struct page" and pure PFN pages */
-#define VM_PINNED 0x10000000 /* Disable faults for the vma */
+#define VM_PINNED 0x20000000 /* Disable faults for the vma */
#ifndef VM_STACK_DEFAULT_FLAGS /* arch can override this */
#define VM_STACK_DEFAULT_FLAGS VM_DATA_DEFAULT_FLAGS
--
Gilles.
next prev parent reply other threads:[~2008-10-10 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 13:07 [Xenomai-help] Bug with Xenomai and xeno_heap: Eeek! page_mapcount(page) went negative! M. Koehrer
2008-10-09 16:06 ` Gilles Chanteperdrix
2008-10-10 6:36 ` M. Koehrer
2008-10-10 8:19 ` M. Koehrer
2008-10-10 9:06 ` Gilles Chanteperdrix [this message]
2008-10-10 11:42 ` M. Koehrer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EF1B17.807@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mathias_koehrer@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.