From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: I-pipe 1.7 breaks mlockall safety check
Date: Tue, 20 Feb 2007 00:26:15 +0100 [thread overview]
Message-ID: <1171927576.18310.40.camel@domain.hid> (raw)
In-Reply-To: <17882.10558.579029.893183@domain.hid>
On Mon, 2007-02-19 at 23:48 +0100, Gilles Chanteperdrix wrote:
> Here comes yet another amendment of the nocow patch, which avoid a race
> between pgd_alloc creating a new pgd, and __ipipe_pin_range_globally not
> seeing the new pgd because its task is not yet in the task
> list. Unfortunately, __ipipe_pin_range_globally becomes an architecture
> dependent function, but at least we should have no race. The patch also
> fixes the issue with munlockall not clearing the VM_LOCKED flag.
Ok, I'm queuing this one for 1.7-04, in order to play safe with 1.7-03
for the upcoming 2.3.1 release. Since the race has always been there
anyway, we have some time ahead to shake this fix over 2.4-devel.
--
Philippe.
prev parent reply other threads:[~2007-02-19 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 13:06 [Xenomai-core] I-pipe 1.7 breaks mlockall safety check Jan Kiszka
2007-02-15 13:56 ` [Xenomai-core] " Philippe Gerum
2007-02-15 13:58 ` Jan Kiszka
2007-02-15 17:25 ` Philippe Gerum
2007-02-16 9:07 ` Jan Kiszka
2007-02-18 23:20 ` Jan Kiszka
2007-02-18 23:31 ` Gilles Chanteperdrix
2007-02-18 23:50 ` Philippe Gerum
2007-02-19 0:20 ` Gilles Chanteperdrix
2007-02-19 7:30 ` Jan Kiszka
2007-02-19 12:31 ` Jan Kiszka
2007-02-19 12:36 ` Philippe Gerum
2007-02-19 21:24 ` Gilles Chanteperdrix
2007-02-19 22:43 ` Philippe Gerum
2007-02-19 8:10 ` Philippe Gerum
2007-02-19 22:48 ` Gilles Chanteperdrix
2007-02-19 23:26 ` Philippe Gerum [this message]
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=1171927576.18310.40.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.