From: Oleg Nesterov <oleg@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Roland Dreier <roland@kernel.org>,
Konstantin Khlebnikov <koct9i@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Omar Ramirez Luna <omar.ramirez@copitl.com>,
Inki Dae <inki.dae@samsung.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-rdma@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] mm: get_user_pages(write,force) refuse to COW in shared areas
Date: Fri, 25 Apr 2014 21:09:31 +0200 [thread overview]
Message-ID: <20140425190931.GA11323@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1404241518510.4454@eggly.anvils>
On 04/24, Hugh Dickins wrote:
>
> On Thu, 24 Apr 2014, Oleg Nesterov wrote:
>
> > So, what do you think about the patch below? It is probably fine in any case,
> > but is there any "strong" reason to follow the gup's behaviour and forbid the
> > anon page in VM_MAYSHARE && !VM_MAYWRITE vma?
>
> I don't think there is a "strong" reason to forbid it.
>
> The strongest reason is simply that it's much safer if uprobes follows
> the same conventions as mm, and get_user_pages() happens to have
> forbidden that all along.
>
> The philosophical reason to forbid it is that the user mmapped with
> MAP_SHARED, and it's merely a kernel-internal detail that we flip off
> VM_SHARED and treat these read-only shared mappings very much like
> private mappings. The user asked for MAP_SHARED, and we prefer to
> respect that by not letting private COWs creep in.
>
> We could treat those mappings even more like private mappings, and
> allow the COWs; but better to be strict about it, so long as doing
> so doesn't give you regressions.
Great, thanks a lot! I was worried I missed something subtle.
And I forgot to mention, there is another reason why I would like to
change uprobes to follow the same convention. I still think it would
be better to kill __replace_page() and use gup(FOLL_WRITE | FORCE)
in uprobe_write_opcode().
> > --- x/kernel/events/uprobes.c
> > +++ x/kernel/events/uprobes.c
> > @@ -127,12 +127,13 @@ struct xol_area {
> > */
> > static bool valid_vma(struct vm_area_struct *vma, bool is_register)
> > {
> > - vm_flags_t flags = VM_HUGETLB | VM_MAYEXEC | VM_SHARED;
> > + vm_flags_t flags = VM_HUGETLB | VM_MAYEXEC;
>
> I think a one-line patch changing VM_SHARED to VM_MAYSHARE would do it,
> wouldn't it? And save you from having to export is_cow_mapping()
> from mm/memory.c. (I used is_cow_mapping() because I had to make the
> test more complex anyway, just to exclude the case which had been
> oddly handled before.)
Indeed, thanks!
Oleg.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Roland Dreier <roland@kernel.org>,
Konstantin Khlebnikov <koct9i@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Omar Ramirez Luna <omar.ramirez@copitl.com>,
Inki Dae <inki.dae@samsung.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-rdma@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] mm: get_user_pages(write,force) refuse to COW in shared areas
Date: Fri, 25 Apr 2014 21:09:31 +0200 [thread overview]
Message-ID: <20140425190931.GA11323@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1404241518510.4454@eggly.anvils>
On 04/24, Hugh Dickins wrote:
>
> On Thu, 24 Apr 2014, Oleg Nesterov wrote:
>
> > So, what do you think about the patch below? It is probably fine in any case,
> > but is there any "strong" reason to follow the gup's behaviour and forbid the
> > anon page in VM_MAYSHARE && !VM_MAYWRITE vma?
>
> I don't think there is a "strong" reason to forbid it.
>
> The strongest reason is simply that it's much safer if uprobes follows
> the same conventions as mm, and get_user_pages() happens to have
> forbidden that all along.
>
> The philosophical reason to forbid it is that the user mmapped with
> MAP_SHARED, and it's merely a kernel-internal detail that we flip off
> VM_SHARED and treat these read-only shared mappings very much like
> private mappings. The user asked for MAP_SHARED, and we prefer to
> respect that by not letting private COWs creep in.
>
> We could treat those mappings even more like private mappings, and
> allow the COWs; but better to be strict about it, so long as doing
> so doesn't give you regressions.
Great, thanks a lot! I was worried I missed something subtle.
And I forgot to mention, there is another reason why I would like to
change uprobes to follow the same convention. I still think it would
be better to kill __replace_page() and use gup(FOLL_WRITE | FORCE)
in uprobe_write_opcode().
> > --- x/kernel/events/uprobes.c
> > +++ x/kernel/events/uprobes.c
> > @@ -127,12 +127,13 @@ struct xol_area {
> > */
> > static bool valid_vma(struct vm_area_struct *vma, bool is_register)
> > {
> > - vm_flags_t flags = VM_HUGETLB | VM_MAYEXEC | VM_SHARED;
> > + vm_flags_t flags = VM_HUGETLB | VM_MAYEXEC;
>
> I think a one-line patch changing VM_SHARED to VM_MAYSHARE would do it,
> wouldn't it? And save you from having to export is_cow_mapping()
> from mm/memory.c. (I used is_cow_mapping() because I had to make the
> test more complex anyway, just to exclude the case which had been
> oddly handled before.)
Indeed, thanks!
Oleg.
next prev parent reply other threads:[~2014-04-25 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:28 [PATCH] mm: get_user_pages(write,force) refuse to COW in shared areas Hugh Dickins
2014-04-04 8:28 ` Hugh Dickins
2014-04-04 12:32 ` Kirill A. Shutemov
2014-04-04 12:32 ` Kirill A. Shutemov
2014-04-04 14:52 ` Hugh Dickins
2014-04-04 14:52 ` Hugh Dickins
2014-04-24 13:30 ` Oleg Nesterov
2014-04-24 13:30 ` Oleg Nesterov
2014-04-24 23:14 ` Hugh Dickins
2014-04-24 23:14 ` Hugh Dickins
2014-04-25 19:09 ` Oleg Nesterov [this message]
2014-04-25 19:09 ` Oleg Nesterov
2014-04-25 20:07 ` Hugh Dickins
2014-04-25 20:07 ` Hugh Dickins
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=20140425190931.GA11323@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=inki.dae@samsung.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=omar.ramirez@copitl.com \
--cc=roland@kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.