On Mon, Dec 11, 2017 at 02:53:58PM -0700, Jason Gunthorpe wrote:
On Mon, Dec 11, 2017 at 10:50:31PM +0100, Greg KH wrote:
On Mon, Dec 11, 2017 at 04:43:44PM -0500, Don Dutile wrote:
On 12/11/2017 04:19 PM, gregkh@linuxfoundation.org wrote:
The patch below does not apply to the 4.14-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to stable@vger.kernel.org.
thanks,
greg k-h
That's b/c this patch needs to be applied (tagged for stable) first:
commit 2e4c85c6edc80fa532b2c7e1eb3597ef4d4bbb8f Author: Parav Pandit parav@mellanox.com Date: Thu Nov 2 15:22:27 2017 +0200
IB/core: Avoid unnecessary return value check Since there is nothing done with non zero return value, such check is avoided. Signed-off-by: Parav Pandit <parav@mellanox.com> Reviewed-by: Daniel Jurgens <danielj@mellanox.com> Signed-off-by: Leon Romanovsky <leon@kernel.org> Signed-off-by: Doug Ledford <dledford@redhat.com>2b2c7e1eb3597ef4d4bbb8f
That patch was not tagged for stable at all :(
It doesn't look like something that should go to -stable to me..
I think we will need to make you a proper 4.14 backport for the 'Only enforce security for InfiniBand' patch.
No, I almost always want the same exact patches that are in Linus's tree. Otherwise the patch you make will be wrong 90% of the time.
thanks,
greg k-h