From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: using vulnerability ids in patches
Date: Thu, 07 Sep 2017 11:40:42 +0200 [thread overview]
Message-ID: <1504777242.6177.2.camel@sipsolutions.net> (raw)
In-Reply-To: <7b09c3d4-a18a-6bc3-6445-8911c088258f@broadcom.com> (sfid-20170907_113805_461947_FBD398F8)
On Thu, 2017-09-07 at 11:38 +0200, Arend van Spriel wrote:
>
> Ok. So doing this I see a number of instances where the CVE-ID is
> mentioned in the commit message, but there are also instances that
> use the 'Fixes:' tag. Does it make sense to use that or does it
> serve another purpose?
Huh, I don't think that makes sense - the Fixes: tag should be for the
commit that introduced the bug. I guess parsers will have to ignore
garbage so it's probably safe, but I don't think you could mine for CVE
fixes that way anyway ...
johannes
next prev parent reply other threads:[~2017-09-07 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 8:40 using vulnerability ids in patches Arend van Spriel
2017-09-07 8:59 ` Johannes Berg
2017-09-07 9:28 ` Arend van Spriel
2017-09-07 9:38 ` Arend van Spriel
2017-09-07 9:40 ` Johannes Berg [this message]
2017-09-07 9:59 ` Arend van Spriel
2017-09-07 12:34 ` Kalle Valo
2017-09-07 19:55 ` Arend van Spriel
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=1504777242.6177.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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