From: Brandon Williams <bmwill@google.com>
To: Stefan Beller <sbeller@google.com>
Cc: gitster@pobox.com, git@vger.kernel.org, ao2@ao2.it
Subject: Re: [PATCH] grep: handle corrupt index files early
Date: Tue, 15 May 2018 10:01:37 -0700 [thread overview]
Message-ID: <20180515170137.GC72551@google.com> (raw)
In-Reply-To: <20180515010425.149200-1-sbeller@google.com>
On 05/14, Stefan Beller wrote:
> Any other caller of 'repo_read_index' dies upon a negative return of
> it, so grep should, too.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>
> Found while reviewing the series
> https://public-inbox.org/git/20180514105823.8378-1-ao2@ao2.it/
>
> builtin/grep.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/builtin/grep.c b/builtin/grep.c
> index 6e7bc76785a..69f0743619f 100644
> --- a/builtin/grep.c
> +++ b/builtin/grep.c
> @@ -488,7 +488,8 @@ static int grep_cache(struct grep_opt *opt, struct repository *repo,
> strbuf_addstr(&name, repo->submodule_prefix);
> }
>
> - repo_read_index(repo);
> + if (repo_read_index(repo) < 0)
> + die("index file corrupt");
Looks good to me!
>
> for (nr = 0; nr < repo->index->cache_nr; nr++) {
> const struct cache_entry *ce = repo->index->cache[nr];
> --
> 2.17.0.582.gccdcbd54c44.dirty
>
--
Brandon Williams
next prev parent reply other threads:[~2018-05-15 17:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:04 [PATCH] grep: handle corrupt index files early Stefan Beller
2018-05-15 12:18 ` Johannes Schindelin
2018-05-15 13:13 ` Duy Nguyen
2018-05-15 16:44 ` Stefan Beller
2018-05-16 15:24 ` Duy Nguyen
2018-05-16 22:21 ` [PATCH 00/11] Stefan Beller
2018-05-16 22:21 ` [PATCH 01/11] grep: handle corrupt index files early Stefan Beller
2018-05-16 22:21 ` [PATCH 02/11] repository: introduce repo_read_index_or_die Stefan Beller
2018-05-19 6:37 ` Duy Nguyen
2018-05-21 18:38 ` Stefan Beller
2018-05-21 18:50 ` Brandon Williams
2018-05-21 19:27 ` Stefan Beller
2018-05-22 15:13 ` Duy Nguyen
2018-05-22 17:49 ` Why do we have both x*() and *_or_die() for "do or die"? Ævar Arnfjörð Bjarmason
2018-05-22 17:55 ` Duy Nguyen
2018-05-22 18:38 ` Jonathan Nieder
2018-05-22 18:04 ` Stefan Beller
2018-05-23 3:19 ` Junio C Hamano
2018-05-16 22:21 ` [PATCH 03/11] builtin/grep: use repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 04/11] submodule: " Stefan Beller
2018-05-16 22:21 ` [PATCH 05/11] builtin/ls-files: " Stefan Beller
2018-05-16 22:21 ` [PATCH 06/11] read_cache: use repo_read_index_or_die with different error messages Stefan Beller
2018-05-16 22:21 ` [PATCH 07/11] rerere: use repo_read_index_or_die Stefan Beller
2018-05-20 17:45 ` Thomas Gummerer
2018-05-21 18:46 ` Stefan Beller
2018-05-16 22:21 ` [PATCH 08/11] check-attr: switch to repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 09/11] checkout-index: switch to repo_read_index Stefan Beller
2018-05-16 22:21 ` [PATCH 10/11] test helpers: switch to repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 11/11] read_cache: convert most calls " Stefan Beller
2018-05-16 22:27 ` Brandon Williams
2018-05-19 6:55 ` Duy Nguyen
2018-05-19 6:54 ` Duy Nguyen
2018-05-19 6:57 ` [PATCH 00/11] Duy Nguyen
2018-05-17 1:36 ` [PATCH] grep: handle corrupt index files early Junio C Hamano
2018-05-17 17:21 ` Stefan Beller
2018-05-17 22:57 ` Junio C Hamano
2018-05-15 17:01 ` Brandon Williams [this message]
2018-05-15 23:58 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2018-05-15 20:00 [PATCHv2 0/3] Reroll of sb/submodule-merge-in-merge-recursive Stefan Beller
2018-05-15 20:00 ` [PATCH] grep: handle corrupt index files early Stefan Beller
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=20180515170137.GC72551@google.com \
--to=bmwill@google.com \
--cc=ao2@ao2.it \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).