Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
From: David Miller <davem@xxxxxxxxxxxxx>
Date: Sun, 14 May 2017 20:44:04 -0400 (EDT)
Cc: hch@xxxxxx, netdev@xxxxxxxxxxxxxxx, linux-rdma@xxxxxxxxxxxxxxx, stable@xxxxxxxxxxxxxxx, ubraun@xxxxxxxxxxxxxxxxxx
In-reply-to: <1494788929.21774.1.camel@sandisk.com>

From: Bart Van Assche <Bart.VanAssche@xxxxxxxxxxx>
Date: Sun, 14 May 2017 19:08:50 +0000

> What is your plan to avoid that applications start using and
> depending on AF_SMC?

The API is out there already so we are out of luck, and neither
you nor I nor anyone else can "stop" this from happening.

Follow-Ups:
- Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
  - From: Doug Ledford
- RE: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
  - From: Parav Pandit

References:
- Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
  - From: Christoph Hellwig
- Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
  - From: David Miller
- Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
  - From: Bart Van Assche

Prev by Date: v4.11.1 build: 0 failures 0 warnings (v4.11.1)
Next by Date: RE: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Previous by thread: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Next by thread: RE: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]