[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 7 Jul 2008 10:41:53 -0400
From: John Blackwood <john.blackwood@...r.com>
To: David Rientjes <rientjes@...gle.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <lee.schermerhorn@...com>,
Joe Korty <joe.korty@...r.com>
Subject: Re: [bug ?] do_get_mempolicy()
> Subject: Re: [bug ?] do_get_mempolicy()
> From: David Rientjes <rientjes@...gle.com>
> Date: Mon, 7 Jul 2008 03:05:28 -0400
> To: "Blackwood, John" <john.blackwood@...r.com>
> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <lee.schermerhorn@...com>, "Korty, Joe"
<joe.korty@...r.com>
>
> On Thu, 3 Jul 2008, David Rientjes wrote:
>
> > > You're right, the flags member of struct mempolicy has subsequently
> > > changed to carry "internal" flags that are not supposed to be
exposed to
> > > userspace via the get_mempolicy() API.
> > >
>
> John, please give 2.6.26-rc9 a try and let me know if there's any
> outstanding issues.
Hi David,
get_mempolicy()/do_get_mempolicy() is working fine for me now.
Thanks for your help and quick response.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists