Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265943AbUFTUeK (ORCPT ); Sun, 20 Jun 2004 16:34:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265944AbUFTUeK (ORCPT ); Sun, 20 Jun 2004 16:34:10 -0400 Received: from [80.72.36.106] ([80.72.36.106]:21120 "EHLO alpha.polcom.net") by vger.kernel.org with ESMTP id S265943AbUFTUeH (ORCPT ); Sun, 20 Jun 2004 16:34:07 -0400 Date: Sun, 20 Jun 2004 22:34:06 +0200 (CEST) From: Grzegorz Kulewski To: Nick Piggin Cc: Linus Torvalds , Linux Kernel Mailing List , Andrew Morton Subject: Re: Memory and rsync problem with vanilla 2.6.7 In-Reply-To: <40D5A305.80807@yahoo.com.au> Message-ID: References: <20040426013944.49a105a8.akpm@osdl.org> <40D508E8.2050407@yahoo.com.au> <40D5A305.80807@yahoo.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 31 On Mon, 21 Jun 2004, Nick Piggin wrote: > Grzegorz Kulewski wrote: > >>>Well it doesn't seem to have caused too much trouble as yet... But it > >>>is the obvious candidate if your problems continue. If you are not a > >>>bk user, the attached patch will also revert that change. > >> > >>Thanks, I will test it soon and I will report results. But I am not saying > >>it is a bug - maybe it is simply change that can lead to problems with > >>insane debug options but itself is good? > > > > > > Are you sure that this is good patch against vanilla 2.6.7? It gives me > > 2 failed hunks (both normal and -R)... Should I merge it manually? > > You're right here's the correct one. No, it is not. GCC complains about priority undeclared. It should be probably sc->priority (I changed it this way). Looks like you do not know how to code in C ;-). Thanks, Grzegorz Kulewski - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/