netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: butt3rflyh4ck <butterflyhuangxx@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	butt3rflyh4ck <butterflyhhuangxx@gmail.com>,
	bjorn.andersson@linaro.org
Subject: Re: [PATCH] net: qrtr: fix another OOB Read in qrtr_endpoint_post
Date: Thu, 19 Aug 2021 23:24:39 +0300	[thread overview]
Message-ID: <763a3f4d-9edc-bb0d-539c-c97309a4975d@gmail.com> (raw)
In-Reply-To: <CAFcO6XMTiEmAfVJ4rwdeB6QQ7s3B-1hx3LJpa-StCb-WJwasPg@mail.gmail.com>

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 :)




With regards,
Pavel Skripkin

  reply	other threads:[~2021-08-19 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 18:14 [PATCH] net: qrtr: fix another OOB Read in qrtr_endpoint_post butt3rflyh4ck
2021-08-19 19:16 ` Jakub Kicinski
2021-08-19 19:53   ` Pavel Skripkin
2021-08-19 20:06     ` butt3rflyh4ck
2021-08-19 20:24       ` Pavel Skripkin [this message]
2021-08-19 21:02         ` Jakub Kicinski
2021-08-19 21:16           ` Pavel Skripkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=763a3f4d-9edc-bb0d-539c-c97309a4975d@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=butterflyhhuangxx@gmail.com \
    --cc=butterflyhuangxx@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).