linux-kernel - Re: linux-next: error while fetching the spi-nor tree

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFynbxKc9TgUvcDkMHUn1bnG8pf1MfYgxnHo88LCaVpFqg@mail.gmail.com>
Date:   Tue, 12 Dec 2017 14:53:46 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: error while fetching the spi-nor tree

On Tue, Dec 12, 2017 at 1:24 PM, Cyrille Pitchen
<cyrille.pitchen@...ev4u.fr> wrote:
>
> I don't see anything wrong when fetching the tree or when browsing the
> web server:
> http://git.infradead.org/l2-mtd.git/shortlog/refs/heads/spi-nor/next

There's definitely something funky there.

  http://git.infradead.org/l2-mtd.git/commitdiff/f3203415105860e811f4ee9508efd009c9e6525e
  http://git.infradead.org/l2-mtd.git/commitdiff/7a6843af9089b01eab266bbee0ed19f98f09a94a

both show "no differences found". I suspect that's because of git diff
failing due to missing objects.

Most likely reason? Something like an unsafe garbage collect / prune
operation at infradead.org at the same time as you pushed. I don't
know what infradead.org does, but you can definitely do bad things
maintaining a git tree.

I would suggest doing a force-push back to some known-good state, and
then pushing it out again.

Ie, something like

    git push --force infradead.org:l2-mtd.git v4.15-rc1:master

to reset the master branch to v4.15-rc1, and then pushing out again.
And then asking whoever maintains the infradead git trees if something
odd happened..

              Linus