From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH v2] net/mlx4_en: fix potential use-after-free with
 dma_unmap_page
Date: Wed, 02 May 2018 10:26:09 -0400 (EDT)
Message-ID: <20180502.102609.1429982179942319879.davem@davemloft.net>
References: <1524715234-20002-1-git-send-email-srn@prgmr.com>
        <20180427.194859.554972405986118921.davem@davemloft.net>
        <5ee8574e-154c-3fa6-8b29-09fae1d08861@mellanox.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: srn@prgmr.com, yishaih@mellanox.com, netdev@vger.kernel.org
To: tariqt@mellanox.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:60584 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751548AbeEBO0M (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 2 May 2018 10:26:12 -0400
In-Reply-To: <5ee8574e-154c-3fa6-8b29-09fae1d08861@mellanox.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Tariq Toukan <tariqt@mellanox.com>
Date: Wed, 2 May 2018 16:50:28 +0300

> This patch fixes an issue existing in old kernels. It is not relevant
> per latest code.
> 
> So I'm not sure about the process. After I review it, do I just submit
> it again for -stable?

If that's the case, yes that is what you do, just submit it for -stable
and add a note to the top of the commit message body that says something
like:

	[ Not relevant upstream, therefore no upstream commit. ]

As -stable submissions have to say what their upstream commit ID is
otherwise.

CC: me on the submission, thank you.

Thanks.