Re: [GIT PULL] aio: changes for 3.19
From: Kirill A. Shutemov
Date: Sun Dec 14 2014 - 18:02:47 EST
On Sun, Dec 14, 2014 at 02:13:36PM -0800, Andrew Morton wrote:
> On Sun, 14 Dec 2014 16:52:21 -0500 Benjamin LaHaise <bcrl@xxxxxxxxx> wrote:
> > On Sun, Dec 14, 2014 at 01:47:32PM -0800, Linus Torvalds wrote:
> > > On Sun, Dec 14, 2014 at 12:22 PM, Benjamin LaHaise <bcrl@xxxxxxxxx> wrote:
> > > >
> > > > Pavel Emelyanov (1):
> > > > aio: Make it possible to remap aio ring
> > >
> > > So quite frankly, I think this should have had more acks from VM
> > > people. The patch looks ok to me, but it took me by surprise, and I
> > > don't see much any discussion about it on linux-mm either..
> > Sadly, nobody responded. Maybe akpm can chime in on this change (included
> > below for ease of review and akpm added to the To:)?
> > -ben
> > --
> > "Thought is the essence of where you are now."
> > commit e4a0d3e720e7e508749c1439b5ba3aff56c92976
> > Author: Pavel Emelyanov <xemul@xxxxxxxxxxxxx>
> > Date: Thu Sep 18 19:56:17 2014 +0400
> > aio: Make it possible to remap aio ring
> The patch appears to be a bugfix which coincidentally helps CRIU?
> If it weren't for the bugfix part, I'd be asking "why not pass the
> desired virtual address into io_setup()?".
But it seems the problem is bigger than what the patch fixes. To me we are
too permisive on what vma can be remapped.
How can we know that it's okay to move vma around for random driver which
provide .mmap? Or I miss something obvious?
Kirill A. Shutemov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/