grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Kiper <daniel.kiper@oracle.com>
To: grub-devel@gnu.org
Cc: alec.r.brown@oracle.com, amakhalov@vmware.com,
	arvidjaar@gmail.com, chris.coulson@canonical.com,
	darren.kenny@oracle.com, development@efficientek.com,
	dja@axtens.net, git@xen0n.name, jag.raman@oracle.com,
	jan.setjeeilers@oracle.com, kanth.ghatraju@oracle.com,
	konrad.wilk@oracle.com, mbenatto@redhat.com,
	pfsmorigo@canonical.com, phcoder@gmail.com, pjones@redhat.com,
	ps@pks.im, ross.philipson@oracle.com
Subject: GRUB Coverity x86_64/EFI and ARM64/EFI runs - 0 outstanding defects
Date: Tue, 28 Nov 2023 17:59:31 +0100	[thread overview]
Message-ID: <ZWYcc6RJ8GbmngAb@tomti.i.net-space.pl> (raw)

Hi,

It is our pleasure to inform you that we were able to achieve 0 outstanding
defects for the GRUB Coverity x86_64/EFI and ARM64/EFI runs. We did analysis
of 629 issues and fixed 535 of them. The rest has been dismissed mostly as
false positives. This work allowed us to improve overall GRUB code quality,
reliability and security. We will continue using the Coverity to verify
correctness of newly introduced code and existing one.

The Coverity analysis and fixing of reported issues was initiated by Andrei
Borzenkov in 2014. Later Vladimir Serbinenko joined and together continued this
work until 2017. We restarted using the Coverity analyzer in 2020, when we were
fixing BootHole security vulnerability and other issues. It took us 3 years to
do analysis of all Coverity issues not solved earlier. It was very tedious
process requiring hundreds of hours of code analysis done by many people. We
think it is important to name all, in alphabetical order, who tirelessly worked
to null out all defects reported by the Coverity:
  - Alec Brown (Oracle),
  - Alexey Makhalov (VMware),
  - Andrei Borzenkov,
  - Chris Coulson (Canonical),
  - Daniel Axtens,
  - Darren Kenny (Oracle),
  - Glenn Washburn,
  - Jagannathan Raman (Oracle),
  - Jan Setje-Eilers (Oracle),
  - Konrad Rzeszutek Wilk (Oracle),
  - Marco A Benatto (Red Hat),
  - Patrick Steinhardt,
  - Paulo Flabiano Smorigo (Canonical),
  - Ross Philipson (Oracle),
  - Vladimir Serbinenko,
  - WANG Xuerui.

Thank you for doing this work guys! This success would not be possible without you!

Daniel

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

             reply	other threads:[~2023-11-28 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 16:59 Daniel Kiper [this message]
2023-11-28 17:57 ` GRUB Coverity x86_64/EFI and ARM64/EFI runs - 0 outstanding defects Darren Kenny
2023-12-01 17:06   ` Daniel Kiper

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=ZWYcc6RJ8GbmngAb@tomti.i.net-space.pl \
    --to=daniel.kiper@oracle.com \
    --cc=alec.r.brown@oracle.com \
    --cc=amakhalov@vmware.com \
    --cc=arvidjaar@gmail.com \
    --cc=chris.coulson@canonical.com \
    --cc=darren.kenny@oracle.com \
    --cc=development@efficientek.com \
    --cc=dja@axtens.net \
    --cc=git@xen0n.name \
    --cc=grub-devel@gnu.org \
    --cc=jag.raman@oracle.com \
    --cc=jan.setjeeilers@oracle.com \
    --cc=kanth.ghatraju@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mbenatto@redhat.com \
    --cc=pfsmorigo@canonical.com \
    --cc=phcoder@gmail.com \
    --cc=pjones@redhat.com \
    --cc=ps@pks.im \
    --cc=ross.philipson@oracle.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).