| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 12 Apr 2010 22:20:48 +0200 From: Pavel Machek <pavel@....cz> To: Eric B Munson <ebmunson@...ibm.com> Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org, rolandd@...co.com, peterz@...radead.org, mingo@...e.hu Subject: Re: [PATCH] ummunotify: Userspace support for MMU notifications Hi! > I am resubmitting this patch because I believe that the discussion > has shown this to be an acceptable solution. I have fixed the 32 bit > build errors, but other than that change, the code is the same as > Roland's V3 patch. > > From: Roland Dreier <rolandd@...co.com> > > As discussed in <http://article.gmane.org/gmane.linux.drivers.openib/61925> > and follow-up messages, libraries using RDMA would like to track > precisely when application code changes memory mapping via free(), > munmap(), etc. Current pure-userspace solutions using malloc hooks > and other tricks are not robust, and the feeling among experts is that > the issue is unfixable without kernel help. I do not know. I still believe that this does not belong in the kernel; application should not need to trace itself to know what it does. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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