linux-kernel - Re: Linux 3.1-rc7

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]

Date:	Tue, 27 Sep 2011 16:31:20 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnaud Lacombe <lacombar@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.1-rc7

On Tue, Sep 27, 2011 at 4:25 PM, Arnaud Lacombe <lacombar@...il.com> wrote:
>
> What is strange is that I moved from -rc7 to -rc8 with:
>
> % git reset --hard v3.1-rc8

Git optimizes all the filesystem operations heavily. That means that
files that have not changed between two releases and are clean (and
match) in the index are not re-written by a git reset.

You can obviously always force a re-write by removing all files and
then doing the reset, but it should never be necessary under normal
circumstances.

> which should have reset the corrupted file. FYI, the machine is
> running 2.6.35.13-91.fc14.x86_64. Something's smelly with that kernel
> :-/

More likely something is smelly with your filesystem or memory. A few
bits flipped on disk or in the page cache would do it, and git has
caught corruption like that before.

Do you still have the bad tree around? Because it migth be interesting
to see what the corruption pattern is if you do.

                       Linus
--
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/