netdev - Re: [PATCH v2] net/mlx4_en: fix potential use-after-free with dma_unmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180502.102609.1429982179942319879.davem@davemloft.net>
Date:   Wed, 02 May 2018 10:26:09 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     tariqt@...lanox.com
Cc:     srn@...mr.com, yishaih@...lanox.com, netdev@...r.kernel.org
Subject: Re: [PATCH v2] net/mlx4_en: fix potential use-after-free with
 dma_unmap_page

From: Tariq Toukan <tariqt@...lanox.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.