From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: protection domain question
Date: Sun, 10 Apr 2016 07:55:11 -0700 [thread overview]
Message-ID: <20160410145511.GB2409@infradead.org> (raw)
In-Reply-To: <570A62B7.9020200-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
On Sun, Apr 10, 2016 at 05:27:03PM +0300, Sagi Grimberg wrote:
> >Is there any good reason to have each kernel driver create it's own PDs
> >instead of simply creating one per device and sticking it into the
> >ib_device structure?
>
> There is a theoretical breach here. Say you're connected with a srp
> channel to a target, and you send out rkey X to your peer. In case
> there is a man-in-the-middle who sniffs it, he can theoretically
> read/write to your rkey by connecting to IPoIB in RC mode (which
> will connect to anyone).
Already, makes sense.
--
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
next prev parent reply other threads:[~2016-04-10 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 19:03 protection domain question Christoph Hellwig
[not found] ` <20160409190331.GA23186-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-04-10 14:27 ` Sagi Grimberg
[not found] ` <570A62B7.9020200-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-04-10 14:55 ` Christoph Hellwig [this message]
[not found] ` <20160410145511.GB2409-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-04-10 19:10 ` santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA
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=20160410145511.GB2409@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@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