All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"apw@canonical.com" <apw@canonical.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH 1/1] Drivers: hv: Implement the file copy service
Date: Thu, 9 Jan 2014 12:14:36 -0800	[thread overview]
Message-ID: <20140109201436.GA16425@kroah.com> (raw)
In-Reply-To: <20140109200921.GT30234@mwanda>

On Thu, Jan 09, 2014 at 11:09:21PM +0300, Dan Carpenter wrote:
> We've had this discussion before where you urge me to trust the host...
> 
>  Problem: This code is racy.
> Solution: The host will only send one message at a time.
> 
> Now I have to audit the user space code on the host and I don't feel
> like doing that so you win.
> 
> I wish we had a better way to do IPC.  If kdbus were ready, that might
> have worked for this, and it's a better solution because both sender and
> reciever code will be written in a less trusting way.

kdbus is almost ready, it might make 3.15, depending on the result of
work that is happening at linux.conf.au and FOSDEM.

If it would be a better solution for this, that's even more reason to
get kdbus merged soon, no need to add something that doesn't really
work.

But, how will kdbus help with this?  It's a userspace <-> userspace
message transmission bus, would you want the kernel to be a receiver or
sender here?

thanks,

greg k-h

  reply	other threads:[~2014-01-09 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 23:48 [PATCH 1/1] Drivers: hv: Implement the file copy service K. Y. Srinivasan
2014-01-08 23:15 ` Greg KH
2014-01-09  7:39 ` Dan Carpenter
2014-01-09 11:18   ` [PATCH 2/2] Drivers: hv: balloon: Online the hot-added memory "in context" " Victor Miasnikov
2014-01-09 18:55   ` KY Srinivasan
2014-01-09 20:09     ` Dan Carpenter
2014-01-09 20:14       ` gregkh [this message]
2014-01-09 21:13         ` KY Srinivasan
2014-01-09 21:05       ` KY Srinivasan
2014-01-10  9:40         ` Dan Carpenter
2014-01-09 12:03 ` Olaf Hering
2014-01-09 18:01   ` KY Srinivasan

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=20140109201436.GA16425@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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.