git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Steadmon <steadmon@google.com>
To: git@vger.kernel.org
Cc: eric.sesterhenn@x41-dsec.de, jarlob@gmail.com
Subject: [PATCH 0/3] fuzz: port OSS-Fuzz tests back to Git
Date: Thu, 10 Oct 2024 14:11:52 -0700	[thread overview]
Message-ID: <cover.1728594659.git.steadmon@google.com> (raw)

Git's fuzz tests are run continuously as part of OSS-Fuzz [1]. Several
additional fuzz tests have been contributed directly to OSS-Fuzz;
however, these tests are vulnerable to bitrot because they are not built
during Git's CI runs, and thus breaking changes are much less likely to
be noticed by Git contributors.

OSS-Fuzz's recommended setup is for tests to live in the repository of
the code they test and to be built along with other tests [1].

Port some of these tests back to the Git project, so that they can be
built and tested during our normal development workflow and CI, and as
such avoid future bitrot.

[1] https://google.github.io/oss-fuzz/advanced-topics/ideal-integration/


Eric Sesterhenn (3):
  fuzz: port fuzz-credential-from-url-gently from OSS-Fuzz
  fuzz: port fuzz-parse-attr-line from OSS-Fuzz
  fuzz: port fuzz-url-decode-mem from OSS-Fuzz

 Makefile                                   |  3 ++
 attr.c                                     | 38 +------------------
 attr.h                                     | 43 ++++++++++++++++++++++
 ci/run-build-and-minimal-fuzzers.sh        | 15 +++++++-
 oss-fuzz/.gitignore                        |  3 ++
 oss-fuzz/fuzz-credential-from-url-gently.c | 32 ++++++++++++++++
 oss-fuzz/fuzz-parse-attr-line.c            | 39 ++++++++++++++++++++
 oss-fuzz/fuzz-url-decode-mem.c             | 43 ++++++++++++++++++++++
 8 files changed, 177 insertions(+), 39 deletions(-)
 create mode 100644 oss-fuzz/fuzz-credential-from-url-gently.c
 create mode 100644 oss-fuzz/fuzz-parse-attr-line.c
 create mode 100644 oss-fuzz/fuzz-url-decode-mem.c


base-commit: 159f2d50e75c17382c9f4eb7cbda671a6fa612d1
-- 
2.47.0.rc1.288.g06298d1525-goog


             reply	other threads:[~2024-10-10 21:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 21:11 Josh Steadmon [this message]
2024-10-10 21:11 ` [PATCH 1/3] fuzz: port fuzz-credential-from-url-gently from OSS-Fuzz Josh Steadmon
2024-10-11  9:13   ` Oswald Buddenhagen
2024-10-11 16:35     ` Junio C Hamano
2024-10-14 20:35     ` Josh Steadmon
2024-10-14 20:43   ` Josh Steadmon
2024-10-10 21:11 ` [PATCH 2/3] fuzz: port fuzz-parse-attr-line " Josh Steadmon
2024-10-10 21:11 ` [PATCH 3/3] fuzz: port fuzz-url-decode-mem " Josh Steadmon
2024-10-10 21:34 ` [PATCH 0/3] fuzz: port OSS-Fuzz tests back to Git Junio C Hamano
2024-10-14 21:04 ` [PATCH v2 " Josh Steadmon
2024-10-14 21:04   ` [PATCH v2 1/3] fuzz: port fuzz-credential-from-url-gently from OSS-Fuzz Josh Steadmon
2024-10-14 21:04   ` [PATCH v2 2/3] fuzz: port fuzz-parse-attr-line " Josh Steadmon
2024-10-14 21:04   ` [PATCH v2 3/3] fuzz: port fuzz-url-decode-mem " Josh Steadmon

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=cover.1728594659.git.steadmon@google.com \
    --to=steadmon@google.com \
    --cc=eric.sesterhenn@x41-dsec.de \
    --cc=git@vger.kernel.org \
    --cc=jarlob@gmail.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 NNTP newsgroup(s).