From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-aio@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Pavel Emelyanov <xemul@parallels.com>,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: [GIT PULL] aio: changes for 3.19
Date: Mon, 15 Dec 2014 01:02:08 +0200 [thread overview]
Message-ID: <20141214230208.GA9217@node.dhcp.inet.fi> (raw)
In-Reply-To: <20141214141336.a0267e95.akpm@linux-foundation.org>
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@kvack.org> 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@kvack.org> 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@parallels.com>
> > 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-12-14 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 20:22 Benjamin LaHaise
2014-12-14 21:47 ` Linus Torvalds
2014-12-14 21:52 ` Benjamin LaHaise
2014-12-14 22:09 ` Linus Torvalds
2014-12-14 22:13 ` Andrew Morton
2014-12-14 22:39 ` Benjamin LaHaise
2014-12-15 5:53 ` Andrew Morton
2014-12-14 23:02 ` Kirill A. Shutemov [this message]
2014-12-14 23:08 ` Benjamin LaHaise
2014-12-14 23:11 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141214230208.GA9217@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=dmonakhov@openvz.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox