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: Wed, 16 Sep 2009 22:43:45 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "Michael S. Tsirkin" <mst@...hat.com> Cc: netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, mingo@...e.hu, linux-mm@...ck.org, hpa@...or.com, aarcange@...hat.com Subject: Re: [PATCHv2 1/2] mm: export use_mm/unuse_mm to modules On Thu, 17 Sep 2009 08:38:18 +0300 "Michael S. Tsirkin" <mst@...hat.com> wrote: > Hi Andrew, > On Tue, Aug 11, 2009 at 03:10:10PM -0700, Andrew Morton wrote: > > On Wed, 12 Aug 2009 00:27:52 +0300 > > "Michael S. Tsirkin" <mst@...hat.com> wrote: > > > > > vhost net module wants to do copy to/from user from a kernel thread, > > > which needs use_mm (like what fs/aio has). Move that into mm/ and > > > export to modules. > > > > OK by me. Please include this change in the virtio patchset. Which I > > shall cheerfully not be looking at :) > > The virtio patches are somewhat delayed as we are ironing out the > kernel/user interface with Rusty. Can the patch moving use_mm to mm/ be > applied without exporting to modules for now? This will make it easier > for virtio which will only have to patch in the EXPORT line. That was 10,000 patches ago. > I also have a small patch optimizing atomic usage in use_mm (which I did for > virtio) and it's easier to apply it if the code is in the new place. > > If ok, pls let me know and I'll post the patch without the EXPORT line. Please just send them all out. -- 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