linux-kernel - Re: build breakage -- paravirt_{alloc,free}

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

Message-ID: <3f9a31f40901120352x5241048x4f0a52c0b8ad44b0@mail.gmail.com>
Date:	Mon, 12 Jan 2009 17:22:05 +0530
From:	"Jaswinder Singh Rajput" <jaswinderlinux@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Jiri Kosina" <jkosina@...e.cz>,
	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	linux-kernel@...r.kernel.org,
	"Jaswinder Singh Rajput" <jaswinderrajput@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: build breakage -- paravirt_{alloc,free}_ldt

On Mon, Jan 12, 2009 at 5:09 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Jaswinder Singh Rajput <jaswinderlinux@...il.com> wrote:
>> It works for me for my old 166 MHz pentium machine after crashing the
>> system, 'git diff' tells which files are broken ;-)
>
> That's cool from Git :-)
>
> Thinking about it, it might not necessarily detect all corruption patterns
> though: git diff is sys_lstat() driven - so if a corruption corrupts a
> single block on the filesystem (in a working tree file), git diff wont
> know about that.
>

I face these problems very often when I compile kernel in old 166 MHz
machine system often freezes during compilation and that machine is
having ext2 filesystem after rebooting the system some inodes are
deleted and then I start getting funny errors. So 'git diff' tells me
which files are broken and then 'git reset --hard origin' again
provide me working system :-)

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