From: Jonathan Tan <jonathantanmy@google.com>
To: Josip Sokcevic <sokcevic@google.com>
Cc: Jonathan Tan <jonathantanmy@google.com>,
git@vger.kernel.org, git@jeffhostetler.com
Subject: Re: [PATCH v2] diff-lib: Fix check_removed when fsmonitor is on
Date: Thu, 7 Sep 2023 10:22:48 -0700 [thread overview]
Message-ID: <20230907172248.1789451-1-jonathantanmy@google.com> (raw)
In-Reply-To: <20230907170119.1536694-1-sokcevic@google.com>
Josip Sokcevic <sokcevic@google.com> writes:
> git-diff-index may return incorrect deleted entries when fsmonitor is used in a
> repository with git submodules. This can be observed on Mac machines, but it
> can affect all other supported platforms too.
>
> If fsmonitor is used, `stat *st` may not be initialized. Since `lstat` calls
> aren't not desired when fsmonitor is on, skip the entire gitlink check using
> the same condition used to initialize `stat *st`.
I think this paragraph is outdated - you'll need to update it to match
the code in this version.
> diff --git a/diff-lib.c b/diff-lib.c
> index d8aa777a73..664613bb1b 100644
> --- a/diff-lib.c
> +++ b/diff-lib.c
> @@ -39,11 +39,22 @@
> static int check_removed(const struct index_state *istate, const struct cache_entry *ce, struct stat *st)
> {
> assert(is_fsmonitor_refreshed(istate));
> - if (!(ce->ce_flags & CE_FSMONITOR_VALID) && lstat(ce->name, st) < 0) {
> - if (!is_missing_file_error(errno))
> - return -1;
> - return 1;
> + if (ce->ce_flags & CE_FSMONITOR_VALID) {
> + /*
> + * Both check_removed() and its callers expect lstat() to have
> + * happened and, in particular, the st_mode field to be set.
> + * Simulate this with the contents of ce.
> + */
> + memset(st, 0, sizeof(*st));
> + st->st_mode = ce->ce_mode;
> + } else {
> + if (lstat(ce->name, st) < 0) {
> + if (!is_missing_file_error(errno))
> + return -1;
> + return 1;
> + }
> }
> +
> if (has_symlink_leading_path(ce->name, ce_namelen(ce)))
> return 1;
> if (S_ISDIR(st->st_mode)) {
I'm on the fence about whether the extra newline is necessary - the "if"
did get bigger, but the code is clear enough without the newline. I lean
towards removing it, to avoid cluttering the diff.
next prev parent reply other threads:[~2023-09-07 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 0:56 Strange diff-index with fsmonitor, submodules Jonathan Tan
2023-08-29 1:20 ` Junio C Hamano
2023-08-29 12:45 ` Jeff Hostetler
2023-08-29 16:57 ` Jeff Hostetler
2023-08-29 17:01 ` Jonathan Tan
2023-09-06 6:02 ` [PATCH] [diff-lib] Fix check_removed when fsmonitor is on Josip Sokcevic
2023-09-06 20:37 ` Jonathan Tan
2023-09-07 17:01 ` [PATCH v2] diff-lib: " Josip Sokcevic
2023-09-07 17:22 ` Jonathan Tan [this message]
2023-09-07 18:07 ` Junio C Hamano
2023-09-07 23:08 ` Josip Sokcevic
2023-09-08 15:00 ` Junio C Hamano
2023-09-11 17:09 ` [PATCH v3] " Josip Sokcevic
2023-09-11 22:53 ` Junio C Hamano
2023-09-12 3:03 ` Josip Sokcevic
2023-09-12 17:07 ` Junio C Hamano
2023-09-14 22:39 ` Josip Sokcevic
2023-09-18 16:35 ` Junio C Hamano
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=20230907172248.1789451-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=sokcevic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.