lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Dec 2012 12:35:00 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Missing tags in my local stable git repo

Hi Greg,

I'm curious if you are removing tags from your git repo on kernel.org.
I've been getting the following errors on my own repos. I have a
linus.git repo that mirrors, Linus's tree, and a stable.git repo based
off of my linus.git and it clones your stable.git tree on kernel.org.
But recently after daily updates and garbage collections, my work repo
that is based off of my stable.git repo gave me this:

error: refs/tags/v2.6.31.1 does not point to a valid object!
error: refs/tags/v2.6.31.10 does not point to a valid object!
error: refs/tags/v2.6.31.11 does not point to a valid object!
error: refs/tags/v2.6.31.12 does not point to a valid object!
error: refs/tags/v2.6.31.2 does not point to a valid object!
error: refs/tags/v2.6.31.3 does not point to a valid object!
error: refs/tags/v2.6.31.4 does not point to a valid object!
error: refs/tags/v2.6.31.5 does not point to a valid object!
error: refs/tags/v2.6.31.6 does not point to a valid object!
error: refs/tags/v2.6.31.7 does not point to a valid object!
error: refs/tags/v2.6.31.8 does not point to a valid object!
error: refs/tags/v2.6.31.9 does not point to a valid object!
error: refs/tags/v2.6.33.1 does not point to a valid object!
error: refs/tags/v2.6.33.2 does not point to a valid object!
error: refs/tags/v2.6.33.3 does not point to a valid object!
error: refs/tags/v2.6.33.4 does not point to a valid object!
error: refs/tags/v2.6.33.5 does not point to a valid object!
error: refs/tags/v2.6.33.6 does not point to a valid object!
error: refs/tags/v2.6.33.7 does not point to a valid object!

This repo has the following alternates:

$ cat .git/objects/info/alternates
/home/rostedt/work/git/nobackup/linus.git/objects
/home/rostedt/work/git/nobackup/stable.git/objects


$ cat ~/work/git/nobackup/stable.git/objects/info/alternates 
/home/rostedt/work/git/nobackup/linus.git//objects

And the stable.git remotes look like:

origin  /home/rostedt/work/git/nobackup/linus.git/ (fetch)
origin  /home/rostedt/work/git/nobackup/linus.git/ (push)
stable  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (fetch)
stable  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (push)

My linus.git tree is simply a bare tree that mirrors Linus's tree:

origin  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (fetch)
origin  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (push)

I have a crontab that updates these every night with a 'git remote
update' and once a week they do a 'git gc' on these repos. I notice the
above issues after the git gc.

I'm not sure where the problem arised, but did you do any cleanups of
tags on the stable git repo?

$ git fetch stable v2.6.33.4 
error: Could not read 15b059e0f9e31f0e7f6b5397368054c005949fea
error: Could not read 5e20b95750867086fff98e5c3eaa00c3bc01d8ee
remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 1 (delta 0)
Unpacking objects: 100% (1/1), done.
fatal: bad object 4640b4e7d9919e9629fe8456df94f71658431ef9
error: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git did not send all necessary objects


Again, I'm not sure if this is something with me, or something with the
kernel.org stable tree.

Thanks,

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ