From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>, "davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"ubraun@linux.vnet.ibm.com" <ubraun@linux.vnet.ibm.com>
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Date: Sun, 14 May 2017 19:08:50 +0000 [thread overview]
Message-ID: <1494788929.21774.1.camel@sandisk.com> (raw)
In-Reply-To: <20170514.115116.499149210596634881.davem@davemloft.net>
On Sun, 2017-05-14 at 11:51 -0400, David Miller wrote:
> From: Christoph Hellwig <hch@lst.de>
> Date: Sun, 14 May 2017 07:58:48 +0200
>
> > this patch has not been superceeded by anything, can you explain why
> > it has been marked as such in patchworks?
>
> I think you're being overbearing by requiring this to be marked BROKEN
> and I would like you to explore other ways with the authors to fix
> whatever perceived problems you think SMC has.
>
> You claim that this is somehow "urgent" is false. You can ask
> distributions to disable SMC or whatever in the short term if it
> reallly, truly, bothers you.
Hello Dave,
There is agreement that the user-space API for using the SMC protocol must
be changed, namely by dropping AF_SMC and by making applications use the
SMC protocol through socket(AF_INET..., SOCK_STREAM, ...). What is your
plan to avoid that applications start using and depending on AF_SMC?
Thanks,
Bart.
next prev parent reply other threads:[~2017-05-14 19:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 7:26 [PATCH] net/smc: mark as BROKEN due to remote memory exposure Christoph Hellwig
2017-05-11 14:57 ` Bart Van Assche
2017-05-14 5:58 ` Christoph Hellwig
2017-05-14 15:51 ` David Miller
2017-05-14 19:08 ` Bart Van Assche [this message]
2017-05-15 0:44 ` David Miller
2017-05-15 1:58 ` Parav Pandit
2017-05-16 15:57 ` Doug Ledford
2017-05-16 16:29 ` David Miller
2017-05-16 16:30 ` Christoph Hellwig
2017-05-16 16:33 ` David Miller
2017-05-16 16:35 ` Christoph Hellwig
2017-05-16 16:36 ` Doug Ledford
2017-05-16 16:41 ` David Miller
2017-05-16 17:12 ` Doug Ledford
2017-05-16 16:42 ` Doug Ledford
2017-05-16 16:49 ` David Miller
2017-05-16 17:20 ` Doug Ledford
2017-05-16 17:36 ` David Miller
2017-05-16 18:03 ` Doug Ledford
2017-05-16 18:52 ` David Miller
2017-05-16 19:28 ` Doug Ledford
2017-05-17 20:37 ` Doug Ledford
2017-05-17 22:37 ` Parav Pandit
2017-05-18 0:07 ` Doug Ledford
2017-05-18 4:22 ` Leon Romanovsky
2017-05-15 6:41 ` Sagi Grimberg
2017-05-15 7:18 ` Leon Romanovsky
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=1494788929.21774.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ubraun@linux.vnet.ibm.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 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).