On Mon, Oct 14, 2013 at 06:31:37PM -0400, Jeff King wrote: > > "git grep" tells me this is the first use of memrchr(), which, > > unlike memchr(), is _GNU_SOURCE-only if I am not mistaken, so we may > > need a fallback definition in the compat/ and NEEDS_MEMRCHR in the > > Makefile, I think. > > Yeah, you are right[1]. I'm happy to re-roll. I wonder if we even need > to worry about a compatibility wrapper. We are already doing pointer > manipulations, and it is probably just as readable to roll the loop by > hand. Here is that re-roll, which does: - cp = memrchr(split->mail_end, '>', len - (split->mail_end - line)); + for (cp = line + len - 1; *cp != '>'; cp--) + ; -- >8 -- Subject: split_ident: parse timestamp from end of line Split_ident currently parses left to right. Given this input: Your Name <email@xxxxxxxxxxx> 123456789 -0500\n We assume the name starts the line and runs until the first "<". That starts the email address, which runs until the first ">". Everything after that is assumed to be the timestamp. This works fine in the normal case, but is easily broken by corrupted ident lines that contain an extra ">". Some examples seen in the wild are: 1. Name <email>-<> 123456789 -0500\n 2. Name <email> <Name<email>> 123456789 -0500\n 3. Name1 <email1>, Name2 <email2> 123456789 -0500\n Currently each of these produces some email address (which is not necessarily the one the user intended) and end up with a NULL date (which is generally interpreted as the epoch by "git log" and friends). But in each case we could get the correct timestamp simply by parsing from the right-hand side, looking backwards for the final ">", and then reading the timestamp from there. In general, it's a losing battle to try to automatically guess what the user meant with their broken crud. But this particular workaround is probably worth doing. One, it's dirt simple, and can't impact non-broken cases. Two, it doesn't catch a single breakage we've seen, but rather a large class of errors (i.e., any breakage inside the email angle brackets may affect the email, but won't spill over into the timestamp parsing). And three, the timestamp is arguably more valuable to get right, because it can affect correctness (e.g., in --until cutoffs). This patch implements the right-to-left scheme described above. We adjust the tests in t4212, which generate a commit with such a broken ident, and now gets the timestamp right. We also add a test that fsck continues to detect the breakage. For reference, here are pointers to the breakages seen (as numbered above): [1] http://article.gmane.org/gmane.comp.version-control.git/221441 [2] http://article.gmane.org/gmane.comp.version-control.git/222362 [3] http://perl5.git.perl.org/perl.git/commit/13b79730adea97e660de84bbe67f9d7cbe344302 Signed-off-by: Jeff King <peff@xxxxxxxx> --- ident.c | 16 +++++++++++++++- t/t4212-log-corrupt.sh | 9 +++++++-- 2 files changed, 22 insertions(+), 3 deletions(-) diff --git a/ident.c b/ident.c index 1c123e6..7d1c79c 100644 --- a/ident.c +++ b/ident.c @@ -233,7 +233,21 @@ int split_ident_line(struct ident_split *split, const char *line, int len) if (!split->mail_end) return status; - for (cp = split->mail_end + 1; cp < line + len && isspace(*cp); cp++) + /* + * Look from the end-of-line to find the trailing ">" of the mail + * address, even though we should already know it as split->mail_end. + * This can help in cases of broken idents with an extra ">" somewhere + * in the email address. Note that we are assuming the timestamp will + * never have a ">" in it. + * + * Note that we will always find some ">" before going off the front of + * the string, because will always hit the split->mail_end closing + * bracket. + */ + for (cp = line + len - 1; *cp != '>'; cp--) + ; + + for (cp = cp + 1; cp < line + len && isspace(*cp); cp++) ; if (line + len <= cp) goto person_only; diff --git a/t/t4212-log-corrupt.sh b/t/t4212-log-corrupt.sh index ec5099b..93c7c36 100755 --- a/t/t4212-log-corrupt.sh +++ b/t/t4212-log-corrupt.sh @@ -13,11 +13,16 @@ test_expect_success 'git log with broken author email' ' git update-ref refs/heads/broken_email $(cat broken_email.hash) ' +test_expect_success 'fsck notices broken commit' ' + git fsck 2>actual && + test_i18ngrep invalid.author actual +' + test_expect_success 'git log with broken author email' ' { echo commit $(cat broken_email.hash) echo "Author: A U Thor <author@xxxxxxxxxxx>" - echo "Date: Thu Jan 1 00:00:00 1970 +0000" + echo "Date: Thu Apr 7 15:13:13 2005 -0700" echo echo " foo" } >expect.out && @@ -30,7 +35,7 @@ test_expect_success 'git log --format with broken author email' ' ' test_expect_success 'git log --format with broken author email' ' - echo "A U Thor+author@xxxxxxxxxxx+" >expect.out && + echo "A U Thor+author@xxxxxxxxxxx+Thu Apr 7 15:13:13 2005 -0700" >expect.out && : >expect.err && git log --format="%an+%ae+%ad" broken_email >actual.out 2>actual.err && -- 1.8.4.1.4.gf327177 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html