{"thread":{"id":"4414","subject":"Integrity check","startedAt":"2006-06-06T22:46:27Z","lastAt":"2006-06-07T00:58:03Z","messageCount":4,"participants":["Kenneth Johansson","Linus Torvalds","Dave Jones"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"21350","messageId":"pan.2006.06.06.22.46.26.518589@canit.se","threadId":"4414","inReplyTo":null,"subject":"Integrity check","fromName":"Kenneth Johansson","fromEmail":"ken@canit.se","sentAt":"2006-06-06T22:46:27Z","receivedAt":"2006-06-06T22:46:27Z","isPatch":false,"sender":{"key":"ken@canit.se","avatar":null},"body":"Iwas doing a git pull that ended badly and I thought that just redoing the\ncommand may help but then git thinks everything is just fine.\n\nAfter a few failed attempts I still have not find a good way to make sure\nthat everything is indeed correct. What is the suggested commands to do\nthat ?\n\n--------\nUpdating from 7705a8792b0fc82fd7d4dd923724606bbfd9fb20 to\n1def630a6a49dda5bc89dfbd86656293640456f0 Checking files out...\n 100% (6311/6311) done\nFast forward\n*** glibc detected *** malloc(): memory corruption: 0x0a703e80 ***\n/home/ken/bin/git-merge: line 56: 14121 Aborted                \ngit-diff-tree -p --stat --summary -M \"$head\" \"$1\" \n\n>git pull\n* refs/heads/origin: same as branch 'master' of\n/delta/kernel/git/linux-2.6/ Already up-to-date.\n[\n"},{"id":"21352","messageId":"Pine.LNX.4.64.0606061550100.5498@g5.osdl.org","threadId":"4414","inReplyTo":"pan.2006.06.06.22.46.26.518589@canit.se","subject":"Re: Integrity check","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-06-06T22:53:33Z","receivedAt":"2006-06-06T22:53:33Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 7 Jun 2006, Kenneth Johansson wrote:\n>\n> Iwas doing a git pull that ended badly and I thought that just redoing the\n> command may help but then git thinks everything is just fine.\n\nWhat happened is that your first pull actually worked fine, but the final \n\"git-diff-tree\" that shows what the pull actually _did_ ended up \nSIGSEGV'ing.\n\nSubsequent pulls won't SIGSEGV, because they dont' have anything to do any \nmore: your state is fine.\n\nI think the SIGSEGV was due to the problem (that Junio already fixed) with \na corrupted heap due to the \"diffstat\" doing bad things for renames.\n\nSo you probably do want to update your git version, but I don't think \nanything bad actually ever happened, apart from the (a) scare and (b) lack \nof diffstat output after the pull.\n\n> After a few failed attempts I still have not find a good way to make sure\n> that everything is indeed correct. What is the suggested commands to do\n> that ?\n\nIn the future, just do \"git fsck-objects --full\" if you're nervous. That \nwill do a full integrity check.\n\n\t\tLinus\n"},{"id":"21353","messageId":"Pine.LNX.4.64.0606061553420.5498@g5.osdl.org","threadId":"4414","inReplyTo":"Pine.LNX.4.64.0606061550100.5498@g5.osdl.org","subject":"Re: Integrity check","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-06-06T22:56:58Z","receivedAt":"2006-06-06T22:56:58Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Tue, 6 Jun 2006, Linus Torvalds wrote:\n> \n> In the future, just do \"git fsck-objects --full\" if you're nervous. That \n> will do a full integrity check.\n\nBtw, this can output some scary-sounding \"unreachable commit xxxxxx\" \nmessages or similar, without that actually necessarily being a problem at \nall. Unreachable objects are normal if you've deleted branches, for \nexample, or if you rebase (or your upstream rebases, like the \"pu\" branch \nin the git archive). \n\nSo if you just see a few unreachable objects, doing a \"git prune\" will get \nrid of them, and they aren't normally any sign of actual trouble.\n\n\t\tLinus\n"},{"id":"21365","messageId":"20060607005803.GA10465@redhat.com","threadId":"4414","inReplyTo":"pan.2006.06.06.22.46.26.518589@canit.se","subject":"Re: Integrity check","fromName":"Dave Jones","fromEmail":"davej@redhat.com","sentAt":"2006-06-07T00:58:03Z","receivedAt":"2006-06-07T00:58:03Z","isPatch":false,"sender":{"key":"davej@redhat.com","avatar":null},"body":"On Wed, Jun 07, 2006 at 12:46:27AM +0200, Kenneth Johansson wrote:\n\n > *** glibc detected *** malloc(): memory corruption: 0x0a703e80 ***\n\nThe last time I saw one of these in git, it turned out to be\ndue to a bug in glibc.  If you're using Fedora/RHEL, there are\nupdates available that fix this problem.\n\n\t\tDave\n\n-- \nhttp://www.codemonkey.org.uk\n"}]}