mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Matt Helsley <matthltc@us.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Pavel Emelyanov <xemul@parallels.com>,
	Kees Cook <keescook@chromium.org>, Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] c/r: prctl: Add ability to set new mm_struct::exe_file v3
Date: Fri, 9 Mar 2012 15:59:01 -0800	[thread overview]
Message-ID: <20120309235901.GE19584@count0.beaverton.ibm.com> (raw)
In-Reply-To: <20120309223932.GB725@moon>

On Sat, Mar 10, 2012 at 02:39:32AM +0400, Cyrill Gorcunov wrote:
> On Fri, Mar 09, 2012 at 02:02:44PM -0800, Matt Helsley wrote:
> ...
> > 
> > Sorry about the other email -- hadn't full caught up on this thread.
> 
> No problem.
> 
> > This is even better, yes.
> >
> 
> Well, in final version I switched back to
> 
> +	if (mm->num_exe_file_vmas)
> +		return -EBUSY;
> 
> simply because it's more flexible than mm->exe_file.
> 
> With mm->exe_file this prctl option become a one-shot
> only, and while at moment our user-space tool can perfectly
> live with that I thought that there is no strict need to
> limit the option this way from the very beginning.

As far as backward compatibility, isn't it better to lift that restriction
later rather than add it? I think the latter would very likely "break"
things whereas the former would not.

I also prefer that restriction because it establishes a bound on how
frequently the symlink can change. Keeping it a one-shot deal makes the
values that show up in tools like top more reliable for admins.

> 
> > Of course I'd prefer it if there was a way to keep num_exe_file_vmas
> > correct and not special-case c/r. The first approximation of a solution
> 
> It remains correct actually. There is no way to map new VM_EXECUTABLE
> from user-space after we've unmapped previous ones, so num_exe_file_vmas
> will remain 0.
> 
> > might be to increment the count whenever a new mmap filp == mm->exe_file
> > and decrement on unmap. I think there are a bunch of details needed to
> > make that work but my feeling is it's do-able. Have you investigated this
> > already and rejected it for some reason (did I miss that discussion
> > somehow?)?
> 
> As far as I understand overall num_exe_file_vmas concept -- we track
> a number of VM_EXECUTABLE with it, so setting new exe_file should not
> change num_exe_file_vmas I think.

True, it's literally correct. However the whole reason for having it
is to turn the mm->exe_file reference into a sort of weak reference
which happens to coincide with counting the number of VM_EXECUTABLE vmas
until you do c/r (really just the restart side of c/r).

Cheers,
	-Matt


  reply	other threads:[~2012-03-09 23:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 16:51 Cyrill Gorcunov
2012-03-08 18:26 ` Oleg Nesterov
2012-03-08 19:03   ` Cyrill Gorcunov
2012-03-08 19:05     ` Oleg Nesterov
2012-03-08 19:25       ` Cyrill Gorcunov
2012-03-08 19:25         ` Oleg Nesterov
2012-03-08 19:36           ` Cyrill Gorcunov
2012-03-08 21:48           ` Cyrill Gorcunov
2012-03-09 12:48             ` Oleg Nesterov
2012-03-09 12:57               ` Cyrill Gorcunov
2012-03-09 13:35                 ` Cyrill Gorcunov
2012-03-09 13:47                   ` Oleg Nesterov
2012-03-09 14:13                     ` Cyrill Gorcunov
2012-03-09 14:26                       ` Oleg Nesterov
2012-03-09 14:42                         ` Cyrill Gorcunov
2012-03-09 15:21                           ` Oleg Nesterov
2012-03-09 15:42                             ` Cyrill Gorcunov
2012-03-09 22:02                               ` Matt Helsley
2012-03-09 22:39                                 ` Cyrill Gorcunov
2012-03-09 23:59                                   ` Matt Helsley [this message]
2012-03-10  7:48                                     ` Cyrill Gorcunov
2012-03-13  2:45                                       ` Matt Helsley
2012-03-13  6:26                                         ` Cyrill Gorcunov
2012-03-13  7:18                                           ` Cyrill Gorcunov
2012-03-13 15:43                                             ` Oleg Nesterov
2012-03-13 16:00                                               ` Cyrill Gorcunov
2012-03-13 16:04                                                 ` Cyrill Gorcunov
2012-03-13 16:44                                                   ` Oleg Nesterov
2012-03-14  1:41                                                   ` Matt Helsley
2012-03-14  5:47                                                     ` Cyrill Gorcunov
2012-03-14 22:21                                                       ` Matt Helsley
2012-03-14 22:48                                                         ` Cyrill Gorcunov
2012-03-14  0:36                                               ` Matt Helsley
2012-03-09 21:46     ` Matt Helsley
2012-03-09 21:52       ` Cyrill Gorcunov
2012-03-08 19:31 ` Kees Cook
2012-03-08 19:40   ` Cyrill Gorcunov
2012-03-08 20:02     ` Andy Lutomirski
2012-03-08 20:06       ` Kees Cook
2012-03-08 20:07       ` Cyrill Gorcunov
2012-03-08 20:15         ` Andy Lutomirski
2012-03-08 20:21           ` Cyrill Gorcunov
2012-03-08 20:24             ` Andy Lutomirski
2012-03-08 20:28               ` Cyrill Gorcunov
2012-03-08 21:57               ` Cyrill Gorcunov
2012-03-08 22:03                 ` Kees Cook
2012-03-08 22:12                   ` Cyrill Gorcunov
2012-03-08 22:14                     ` Kees Cook

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=20120309235901.GE19584@count0.beaverton.ibm.com \
    --to=matthltc@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gorcunov@openvz.org \
    --cc=keescook@chromium.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®