From: Ben Tebulin <tebulin@googlemail.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: Ben Tebulin <tebulin@googlemail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Stefan Beller <stefanbeller@googlemail.com>
Subject: Re: Reproducible, corrupt packfile after fresh git-svn checkout message
Date: Wed, 14 Aug 2013 11:47:13 +0200 [thread overview]
Message-ID: <520B5221.3040308@gmail.com> (raw)
In-Reply-To: <877gfok59m.fsf@linux-k42r.v.cablecom.net>
> My best theory so far:
> malloc()/free() actually use mmap()/munmap() for large allocations.
> mallopt(3) tells me that [...]
Many things I don't grab at first go :-)
Last night I did a long git-bisect of the kernel and was able to
pinpoint a change in the Linux memory management as cause (see my
pre-prepared email I just sent).
Would that fit into your theory?
> You could try to gather some data on this by [...]
Before I dive into that maybe you could throw a quick look at the
causing Kernel change (which reading from the words _could_ be related)
if this fits into the picture?
If yes, I'm happy to try to assist you in further pinning this issue down!
next prev parent reply other threads:[~2013-08-14 9:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52037F47.5010302@exxcellent.de>
[not found] ` <52037F84.9060006@exxcellent.de>
2013-08-08 11:56 ` Reproducible, corrupt packfile after fresh gitml.jexpert
2013-08-08 12:13 ` Thomas Rast
2013-08-08 12:23 ` Reproducible, corrupt packfile after fresh git-svn checkout gitml.jexpert
2013-08-08 12:31 ` Thomas Rast
2013-08-08 13:12 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) gitml.jexpert
2013-08-08 13:18 ` Matthieu Moy
2013-08-08 13:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message gitml.jexpert
2013-08-08 13:34 ` Matthieu Moy
2013-08-08 13:43 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) gitml.jexpert
2013-08-08 14:20 ` Thomas Rast
2013-08-08 14:53 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 " Ben Tebulin
2013-08-08 15:28 ` Thomas Rast
2013-08-08 16:36 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-08 16:48 ` Matthieu Moy
2013-08-08 17:38 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 of 20) Junio C Hamano
2013-08-09 12:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-09 12:54 ` Stefan Beller
2013-08-14 9:29 ` Reproducible, corrupt packfile after fresh git-svn checkouts - IDENTIFIED Ben Tebulin
2013-08-14 9:09 ` Reproducible, corrupt packfile after fresh git-svn checkout message Thomas Rast
2013-08-14 9:47 ` Ben Tebulin [this message]
2013-08-15 9:32 ` Ben Tebulin
2013-08-15 14:46 ` Junio C Hamano
2013-08-08 13:20 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) Thomas Rast
2013-08-08 12:38 ` Reproducible, corrupt packfile after fresh git-svn checkout Matthieu Moy
2013-08-08 12:41 ` Stefan Beller
2013-08-08 12:18 ` Reproducible, corrupt packfile after fresh 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=520B5221.3040308@gmail.com \
--to=tebulin@googlemail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stefanbeller@googlemail.com \
--cc=trast@inf.ethz.ch \
/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.