From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org, mst@redhat.com
Cc: vdavydov@virtuozzo.com, akpm@linux-foundation.org,
rientjes@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exit: clear TIF_MEMDIE after exit_task_work
Date: Mon, 13 Jun 2016 22:52:43 +0900 [thread overview]
Message-ID: <201606132252.IAE00593.OJQSFMtVFOLHOF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20160613115041.GG6518@dhcp22.suse.cz>
Michal Hocko wrote:
> I have checked the vnet code and it doesn't seem to rely on
> copy_from_user/get_user AFAICS. Other users of use_mm() need to copy to
> the userspace only as well. So we should be perfectly safe to OOM reap
> address space even when it is shared by the kthread [1] so this is
> not really needed for the OOM correctness purpose. It would be much
> nicer if the kthread didn't pin the mm for two long outside of the OOM
> handling as well of course but that lowers the priority of the change.
>
> [1] http://lkml.kernel.org/r/20160613112348.GC6518@dhcp22.suse.cz
It seems to me that vhost code relies on copy from the userspace.
use_mm(dev->mm) and unuse_mm(dev->mm) are used inside vhost_worker().
work->fn(work) is initialized by vhost_work_init().
vhost_scsi_open() passes vhost_scsi_complete_cmd_work() and
vhost_scsi_evt_work() as ->fn, and both functions call __get_user().
vhost_scsi_complete_cmd_work() {
vhost_signal() {
vhost_notify() {
__get_user()
}
}
}
vhost_scsi_evt_work() {
vhost_scsi_do_evt_work() {
vhost_get_vq_desc() {
__get_user() / __copy_from_user()
get_indirect() {
copy_from_iter()
}
}
}
}
--
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:[~2016-06-13 13:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 17:02 Vladimir Davydov
2016-02-29 18:21 ` Michal Hocko
2016-02-29 18:44 ` Michal Hocko
2016-03-01 15:52 ` Michal Hocko
2016-03-01 15:57 ` Michael S. Tsirkin
2016-03-01 16:08 ` Michal Hocko
2016-03-01 16:14 ` Michael S. Tsirkin
2016-03-01 16:22 ` Michael S. Tsirkin
2016-03-01 16:35 ` Michal Hocko
2016-03-01 16:46 ` Michael S. Tsirkin
2016-03-01 17:17 ` Michal Hocko
2016-03-01 17:20 ` Michael S. Tsirkin
2016-03-14 16:39 ` Michal Hocko
2016-06-07 12:50 ` Michal Hocko
2016-06-13 11:50 ` Michal Hocko
2016-06-13 13:52 ` Tetsuo Handa [this message]
2016-06-13 14:00 ` Michal Hocko
2016-06-13 18:11 ` Michael S. Tsirkin
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=201606132252.IAE00593.OJQSFMtVFOLHOF@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=rientjes@google.com \
--cc=vdavydov@virtuozzo.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