git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3] fuzz: reorganise the path for existing oss-fuzz fuzzers

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Sep 19, 2022, 11:10 UTC
Message-ID
<220919.86r10762bg.gmgdl@evledraar.gmail.com>
In-Reply-To
<pull.1353.v3.git.1663542495094.gitgitgadget@gmail.com>
On Sun, Sep 18 2022, Arthur Chan via GitGitGadget wrote:
Show 5 quoted lines
> From: Arthur Chan <arthur.chan@adalogics.com>
>
> This patch is aimed to provide a better organisation for oss-fuzz
> fuzzers, allowing more fuzzers for the git project to be added
> in later development.

I don't see any problem with this change per-se, but this rationale really doesn't explain anything in the end to the reader. How does just having x/y-*.c files rather than x-y-*.c allow for more fuzzers to be added? We could also add new fuzzers to the top-level now, why does this change help us to do so.

I suspect the unstated reason is just "adding a lot more would make the top-level cluttered", or perhaps some design reason you hinted at in https://lore.kernel.org/git/2405897f-a774-e0d3-99bb-2185dcbb5432@adalogics.com/ (but I haven't taken the time to fully understand).

So, I'm fine with this v3 as-is, but also wouldn't mind a v4 with an updated commit message to address the above confusion.

Show 13 quoted lines
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,7 +1,7 @@
> -/fuzz-commit-graph
> +/oss-fuzz/fuzz-commit-graph
>  /fuzz_corpora
> -/fuzz-pack-headers
> -/fuzz-pack-idx
> +/oss-fuzz/fuzz-pack-headers
> +/oss-fuzz/fuzz-pack-idx
>  /GIT-BUILD-OPTIONS
>  /GIT-CFLAGS
>  /GIT-LDFLAGS

Speaking of clutter, a much better change here IMO would be to create a /oss-fuzz/.gitignore file, and then move these there. For prior art see:

	git ls-files '**/.gitignore'

Even better (but I'm not sure how this is all used in the end), can we perhaps build those in a .gitignore'd oss-fuzz/.build/.

But maybe not, and in any case that would be a larger change to the Makefile logic, so we can leave it for now, but I do think it makes sense to create a oss-fuzz/.gitignore in a v4.

Previous: Arthur Chan via GitGitGadgetNext: Arthur Chan via GitGitGadget
Message 6 of 9 in “fuzz: reorganise the path for existing oss-fuzz fuzzers”
  1. fuzz: reorganise the path for existing oss-fuzz fuzzersArthur Chan via GitGitGadget, Sep 16, 2022
  2. Junio C HamanoSep 16, 2022
  3. Arthur ChanSep 17, 2022
  4. fuzz: reorganise the path for existing oss-fuzz fuzzersArthur Chan via GitGitGadget, Sep 17, 2022
  5. fuzz: reorganise the path for existing oss-fuzz fuzzersArthur Chan via GitGitGadget, Sep 18, 2022
  6. Ævar Arnfjörð BjarmasonSep 19, 2022
  7. fuzz: reorganise the path for existing oss-fuzz fuzzersArthur Chan via GitGitGadget, Sep 19, 2022
  8. Junio C HamanoSep 19, 2022
  9. Junio C HamanoSep 19, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.