linux-kernel - Re: 2.6.22-rc4-mm1

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: <20070607155913.GW11115@waste.org>
Date:	Thu, 7 Jun 2007 10:59:14 -0500
From:	Matt Mackall <mpm@...enic.com>
To:	WANG Cong <xiyou.wangcong@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: 2.6.22-rc4-mm1

On Thu, Jun 07, 2007 at 11:40:08PM +0800, WANG Cong wrote:
> On Thu, Jun 07, 2007 at 09:04:44AM -0500, Matt Mackall wrote:
> >On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
> >> >> Maybe there's something wrong with ketchup. ;(
> >> >
> >> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
> >> >
> >> >Ketchup simply applies patches, it never touches filenames directly.
> >> >So for something to go wrong here and drop a file in the tree with a
> >> >damaged pathname, you've either got a damaged patch, a bug in patch
> >> >itself, or some form of filesystem corruption.
> >> 
> >> Thanks for your point.
> >> 
> >> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
> >> backuped it as mlguest.c.
> >
> >It'd be interesting to figure out how that happened, still.
> >
> >If your patch file is intact (are you using GPG's signature-checking
> >support?), the most likely explanation is an operating system or
> >filesystem bug.
> 
> Yes, I am using GPG's checking.

Well that gives a pretty solid assurance that the patch you downloaded
matches the one on kernel.org. And that one doesn't contain an
mlguest.c. 

Ketchup doesn't even look inside patches, and patch doesn't invent
names, so something in the bzip2 -> patch(1) -> filesystem chain got
corrupted. Probably not bzip2, as it has CRCs.

Do you have ECC memory?

-- 
Mathematics is the supreme nostalgia of our time.
-
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/