From: George Spelvin <lkml@SDF.ORG>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Bernard Metzler <BMT@zurich.ibm.com>,
linux-kernel@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, Faisal Latif <faisal.latif@intel.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
Bart Van Assche <bvanassche@acm.org>,
lkml@sdf.org
Subject: Re: [RFC PATCH v1 42/50] drivers/ininiband: Use get_random_u32()
Date: Sun, 29 Mar 2020 20:45:01 +0000 [thread overview]
Message-ID: <20200329204501.GF4675@SDF.ORG> (raw)
In-Reply-To: <20200329200213.GG20941@ziepe.ca>
On Sun, Mar 29, 2020 at 05:02:13PM -0300, Jason Gunthorpe wrote:
> On Sun, Mar 29, 2020 at 04:52:04PM +0000, George Spelvin wrote:
>> Many intra-machine networks (like infiniband) are specifically not
>> designed to be robust in the face of malicious actors on the network.
>
> This is not really true at all..
Eep, this came out wrong! Let me clarify:
Many intra-machine networks like SCSI, LPC, HyperTransport, QuickPath,
and I2C are specifically not designed to be robust in the face of malicious
actors on the network/bus.
I don't know, *and was wondering*, whether this is true of Infiniband.
Does that make more sense?
prev parent reply other threads:[~2020-03-29 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 0:21 [RFC PATCH v1 42/50] drivers/ininiband: Use get_random_u32() George Spelvin
2020-03-29 14:36 ` Jason Gunthorpe
2020-03-29 16:31 ` George Spelvin
2020-03-29 15:01 ` Bernard Metzler
2020-03-29 16:52 ` George Spelvin
2020-03-29 20:02 ` Jason Gunthorpe
2020-03-29 20:45 ` George Spelvin [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=20200329204501.GF4675@SDF.ORG \
--to=lkml@sdf.org \
--cc=BMT@zurich.ibm.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shiraz.saleem@intel.com \
/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.