From: Hugh Dickins <hughd@google.com>
To: Oleg Nesterov <oleg@redhat.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 13:07:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1404251254230.6272@eggly.anvils> (raw)
In-Reply-To: <20140425190931.GA11323@redhat.com>
On Fri, 25 Apr 2014, Oleg Nesterov wrote:
>
> 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().
Oh, please please do! I assumed there was a good atomicity reason
for doing it that way, but if you can do it with gup() please do so.
I went off into a little rant about __replace_page() in my reply to you;
but then felt that you had approached with an honest enquiry, and didn't
deserve a rant in response, so I deleted it.
And, of course, I'm conscious that I have from start to finish withheld
my involvement from uprobes, and refused to review that __replace_page()
(beyond insisting that it not be put in a common place for sharing with
KSM, because I just couldn't guarantee it for uprobes). I'm afraid that
it's much like HWPoison to me, a complexity (nastiness?) way beyond what
I have time to support myself.
Hugh
--
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>
prev parent reply other threads:[~2014-04-25 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:28 Hugh Dickins
2014-04-04 12:32 ` Kirill A. Shutemov
2014-04-04 14:52 ` Hugh Dickins
2014-04-24 13:30 ` Oleg Nesterov
2014-04-24 23:14 ` Hugh Dickins
2014-04-25 19:09 ` Oleg Nesterov
2014-04-25 20:07 ` Hugh Dickins [this message]
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=alpine.LSU.2.11.1404251254230.6272@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--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=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox