Git development
 help / color / mirror / Atom feed
From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 0/7] Fix issues pointed out in Git for Windows by Coverity after merging v2.56.0-rc0
Date: Thu, 17 Sep 2026 17:52:29 +0000	[thread overview]
Message-ID: <pull.2231.git.1789667556.gitgitgadget@gmail.com> (raw)

These Coverity reports are new as of this -rc cycle; Apart from the writev
one, I don't think any of these are pressing, in most cases I am still
puzzled why they were reported only now.

Johannes Schindelin (7):
  wrapper: guard writev_in_full() against signed overflow
  gpg-interface: make signature-prefix matching length-aware
  midx: validate incremental MIDX pack IDs
  rerere: do not record failed conflict resolution data
  t/unit-tests: check reftable iterator initialization
  oss-fuzz: handle reftable iterator initialization failures
  test-read-midx: check midx_fill_entry() result

 gpg-interface.c                 | 10 +++++-----
 midx.c                          | 12 +++++++++---
 oss-fuzz/fuzz-reftable.c        | 18 ++++++++++--------
 rerere.c                        | 30 ++++++++++++++++++++++++++----
 t/helper/test-read-midx.c       |  6 +++++-
 t/unit-tests/u-reftable-table.c |  2 +-
 wrapper.c                       |  4 ++++
 7 files changed, 60 insertions(+), 22 deletions(-)


base-commit: 12cb6293d6288865c1a133cf22accbaf99d13eb6
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2231%2Fdscho%2Ffix-coverity-high-severity-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2231/dscho/fix-coverity-high-severity-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/2231
-- 
gitgitgadget

             reply	other threads:[~2026-09-17 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 17:52 Johannes Schindelin via GitGitGadget [this message]
2026-09-17 17:52 ` [PATCH 1/7] wrapper: guard writev_in_full() against signed overflow Johannes Schindelin via GitGitGadget
2026-09-17 17:52 ` [PATCH 2/7] gpg-interface: make signature-prefix matching length-aware Johannes Schindelin via GitGitGadget
2026-09-17 19:32   ` Junio C Hamano
2026-09-18  7:12     ` Johannes Schindelin
2026-09-18  8:59       ` Junio C Hamano
2026-09-17 17:52 ` [PATCH 3/7] midx: validate incremental MIDX pack IDs Johannes Schindelin via GitGitGadget
2026-09-17 17:52 ` [PATCH 4/7] rerere: do not record failed conflict resolution data Johannes Schindelin via GitGitGadget
2026-09-17 19:34   ` Junio C Hamano
2026-09-17 17:52 ` [PATCH 5/7] t/unit-tests: check reftable iterator initialization Johannes Schindelin via GitGitGadget
2026-09-17 17:52 ` [PATCH 6/7] oss-fuzz: handle reftable iterator initialization failures Johannes Schindelin via GitGitGadget
2026-09-17 17:52 ` [PATCH 7/7] test-read-midx: check midx_fill_entry() result Johannes Schindelin via GitGitGadget

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=pull.2231.git.1789667556.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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