All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Andy King <acking@vmware.com>
Cc: netdev@vger.kernel.org
Subject: Re: Problems with VSOCK?
Date: Wed, 20 Feb 2013 17:28:55 -0500	[thread overview]
Message-ID: <2319583.NdTBqk4ibZ@sifl> (raw)
In-Reply-To: <1906719446.2930546.1361398782879.JavaMail.root@vmware.com>

On Wednesday, February 20, 2013 02:19:42 PM Andy King wrote:
> Hi Paul,
> 
> > I'm currently looking at the VSOCK implementation in netdev-next to
> > determine what we need in the way of LSM hooks and I ran into a few
> > things which look rather odd:
> > 
> > * net/vmw_sock/Kconfig
> > 
> > VMWARE_VMCI_SOCKETS depends on VMWARE_VMCI which doesn't look to be
> > defined
> > anywhere, help?  For what it is worth, removing the VMWARE_VMCI dependency
> 
> Ah, I think this is the same problem someone else had a few days ago.  VMCI
> came in via Greg's char-misc-next tree, and it hasn't merged into Dave's
> tree yet.  But the top-level linux-next tree now has all required modules:
> 
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
> 
> Sorry about them coming in from different trees :/

Okay, thanks, I'll grab a copy of the next tree and take a look.  That makes 
much more sense, I was finding it hard to believe that so much was missing :)

-- 
paul moore
security and virtualization @ redhat

      reply	other threads:[~2013-02-20 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 22:11 Problems with VSOCK? Paul Moore
2013-02-20 22:19 ` Andy King
2013-02-20 22:28   ` Paul Moore [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=2319583.NdTBqk4ibZ@sifl \
    --to=pmoore@redhat.com \
    --cc=acking@vmware.com \
    --cc=netdev@vger.kernel.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.