public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, mikuback@linux.microsoft.com
Cc: Bob Feng <bob.c.feng@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Yuwei Chen <yuwei.chen@intel.com>,
	Sean Brogan <sean.brogan@microsoft.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/2] Enable CodeQL Failures and Add New Queries
Date: Tue, 8 Nov 2022 15:21:27 -0800	[thread overview]
Message-ID: <BY3PR19MB4900797AE73DF57A2F94E8D1C83F9@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20221108195132.1463-1-mikuback@linux.microsoft.com>

For the codeql series

Reviewed-by: Sean Brogan <sean.brogan@microsoft.com>

On 11/8/2022 11:51 AM, Michael Kubacki wrote:
> From: Michael Kubacki <michael.kubacki@microsoft.com>
>
> When CodeQL was enabled, the goal was to enable the flow and not
> impact build results. cpp/conditionallyuninitializedvariable was
> the first and only query enabled with all CodeQL results filtered
> out from affecting CI results.
>
> This achieved the goal to enable CodeQL for future changes to build
> upon but always get CodeQL successful runs in the meantime.
>
> This patch series:
> 1. Swaps out that initial "placeholder" query with two queries that
>     can be enabled with no code changes.
> 2. Enables "error" level CodeQL alerts.
> 3. Makes fixes made for a default query
>     cpp/wrong-type-format-argument in BaseTools.
>
> The results for (3) can be seen in the following Code Scanning
> results that show the PR with these changes fixed the alerts raised
> by CodeQL.
>
> PR: https://github.com/tianocore/edk2/pull/3617
>
> Code Scanning results (access may be required):
> https://github.com/tianocore/edk2/security/code-scanning?query=pr%3A3617+tool%3ACodeQL+is%3Aclosed
>
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Yuwei Chen <yuwei.chen@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
>
> Michael Kubacki (2):
>    BaseTools: Fix wrong type of arguments to formatting functions
>    edk2.qls: Allow error severity results and add new queries
>
>   BaseTools/Source/C/EfiRom/EfiRom.c          | 2 +-
>   BaseTools/Source/C/GenFv/GenFvInternalLib.c | 2 +-
>   BaseTools/Source/C/GenFw/Elf32Convert.c     | 2 +-
>   BaseTools/Source/C/GenFw/Elf64Convert.c     | 6 +++---
>   BaseTools/Source/C/GenSec/GenSec.c          | 4 ++--
>   .github/codeql/codeql-config.yml            | 1 -
>   .github/codeql/edk2.qls                     | 4 +++-
>   7 files changed, 11 insertions(+), 10 deletions(-)
>

      parent reply	other threads:[~2022-11-08 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:51 [PATCH v1 0/2] Enable CodeQL Failures and Add New Queries Michael Kubacki
2022-11-08 19:51 ` [PATCH v1 1/2] BaseTools: Fix wrong type of arguments to formatting functions Michael Kubacki
2022-11-08 23:38   ` Michael D Kinney
2022-11-09  0:23     ` [edk2-devel] " Michael Kubacki
2022-11-08 19:51 ` [PATCH v1 2/2] edk2.qls: Allow error severity results and add new queries Michael Kubacki
2022-11-08 23:21 ` Sean [this message]

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-list 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=BY3PR19MB4900797AE73DF57A2F94E8D1C83F9@BY3PR19MB4900.namprd19.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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