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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jun 2007 23:40:08 +0800
From:	WANG Cong <xiyou.wangcong@...il.com>
To:	Matt Mackall <mpm@...enic.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 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.

I think the most possible reason is that source file might be corrupted.
It's hardly the filesystem's fault, since I am using a stable kernel.

>
>Can you reproduce it?

May be very hard.;(

I deleted all the files of that version and download a new version to use.

Thanks!


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