Messages in this thread | | | Date | Tue, 11 May 2004 22:11:22 -0700 | From | Chris Wedgwood <> | Subject | Re: 2.6.6-mm1 |
| |
On Wed, May 12, 2004 at 04:44:25AM +0200, Andrea Arcangeli wrote:
> I'm quite confortable to say that disable_cap_mlock can be dropped > in 2.8
Cool.
> by that time a replacement solution will be implemented and > I don't expect any application learning about the disable_cap_mlock > name, they really shouldn't, only the bootup procedure of the OS > will know about it and only the login/su will learn about the future > replacement.
Agreed. It's hack but it's a simpler hack.
> So I believe the best "hack" is to use the simple disable_cap_mlock > and to concentrate all the efforts on a more flexible solution > involving userspace changes.
I quite agree here too. I guess as things stand right now I'll take either approach IFF it will be yanked in 2.7.x when a better replacement is available.
--cw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |