[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210819140233.5f8d8cd1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 19 Aug 2021 14:02:33 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Pavel Skripkin <paskripkin@...il.com>
Cc: butt3rflyh4ck <butterflyhuangxx@...il.com>,
Manivannan Sadhasivam <mani@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
linux-arm-msm@...r.kernel.org, netdev@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
butt3rflyh4ck <butterflyhhuangxx@...il.com>,
bjorn.andersson@...aro.org
Subject: Re: [PATCH] net: qrtr: fix another OOB Read in qrtr_endpoint_post
On Thu, 19 Aug 2021 23:24:39 +0300 Pavel Skripkin wrote:
> On 8/19/21 11:06 PM, butt3rflyh4ck wrote:
> > Yes, this bug can be triggered without your change. The reason why I
> > point to your commit is to make it easier for everyone to understand
> > this bug.
>
> As I understand, purpose of Fixes: tag is to point to commit where the
> bug was introduced. I could be wrong, so it's up to maintainer to decide
> is this Fixes: tag is needed or not :)
You're right thanks for pointing that out. May it should actually be:
Fixes: 0baa99ee353c ("net: qrtr: Allow non-immediate node routing") ?
Powered by blists - more mailing lists