linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Sean Hefty <pookieween-EMRzualFZlQ@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: handling rdma apps using chroot
Date: Wed, 15 Aug 2012 13:32:14 -0600	[thread overview]
Message-ID: <20120815193214.GB2957@obsidianresearch.com> (raw)
In-Reply-To: <SNT114-DS11B5280C71EEE30408772DADB60-MsuGFMq8XAE@public.gmane.org>

On Wed, Aug 15, 2012 at 12:07:25PM -0700, Sean Hefty wrote:
> I'm looking for ideas on the best way for handling applications which use
> chroot, which results in failures using the rdma libraries.  Specifically,
> and not surprisingly, I see failures reading /sys/class/... and
> /dev/infiniband/...
> 
> For background, I'm trying to run vsftpd over rsockets using the preload
> library with fork support.  vsftpd will run only if I comment out its use of
> chroot.  I can reproduce the issue by inserting a chroot call into rstream.
> 
> Does anyone have any suggestions?

Somehow you need to open the verbs device before doing the choot.. I
think once verbs is open there is no further need for sysfs and dev..

Sounds like you are chrooting before creating the listening socket?

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-08-15 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 19:07 handling rdma apps using chroot Sean Hefty
     [not found] ` <SNT114-DS11B5280C71EEE30408772DADB60-MsuGFMq8XAE@public.gmane.org>
2012-08-15 19:32   ` Jason Gunthorpe [this message]
     [not found]     ` <20120815193214.GB2957-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-08-15 19:44       ` Hefty, Sean
     [not found]         ` <1828884A29C6694DAF28B7E6B8A8237346A89506-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-15 19:58           ` Jason Gunthorpe
     [not found]             ` <20120815195837.GA3880-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-08-15 22:31               ` Hefty, Sean

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=20120815193214.GB2957@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pookieween-EMRzualFZlQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).