From: "Michael S. Tsirkin" <mst@redhat.com>
To: gchen chen <gchen.guomin@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jason Wang <jasowang@redhat.com>, gchen <guominchen@tencent.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] Export mm_update_next_owner function for vhost-net
Date: Mon, 17 Dec 2018 20:41:36 -0500 [thread overview]
Message-ID: <20181217204124-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAEEwsfQ9ARxJCZxy5bY70Aa0HYqwto-gROxT8fvrduNn0MVf=A@mail.gmail.com>
On Tue, Dec 18, 2018 at 09:39:16AM +0800, gchen chen wrote:
> Yes, I think so.
> and i think the point is that unuse_mm() can't directly set tsk->mm=NULL.
So why can't unuse_mm call mm_update_next_owner?
--
MST
next prev parent reply other threads:[~2018-12-18 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 4:47 [PATCH] Export mm_update_next_owner function for vhost-net gchen.guomin
2018-12-13 6:30 ` Jason Wang
2018-12-13 6:30 ` Jason Wang
2018-12-13 9:13 ` 答复: [PATCH] Export mm_update_next_owner function for vhost-net(Internet mail) guominchen(陈国民)
2018-12-17 11:32 ` [PATCH] Export mm_update_next_owner function for vhost-net Christoph Hellwig
[not found] ` <CAEEwsfQ9ARxJCZxy5bY70Aa0HYqwto-gROxT8fvrduNn0MVf=A@mail.gmail.com>
2018-12-18 1:41 ` Michael S. Tsirkin [this message]
2018-12-18 1:41 ` Michael S. Tsirkin
2018-12-17 11:32 ` Christoph Hellwig
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=20181217204124-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gchen.guomin@gmail.com \
--cc=guominchen@tencent.com \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=virtualization@lists.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.