Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262927AbUDDXez (ORCPT ); Sun, 4 Apr 2004 19:34:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262935AbUDDXez (ORCPT ); Sun, 4 Apr 2004 19:34:55 -0400 Received: from fw.osdl.org ([65.172.181.6]:63372 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262927AbUDDXev (ORCPT ); Sun, 4 Apr 2004 19:34:51 -0400 Date: Sun, 4 Apr 2004 16:28:18 -0700 From: "Randy.Dunlap" To: Ben Collins Cc: benh@kernel.crashing.org, marcel.lanz@ds9.ch, linux-kernel@vger.kernel.org Subject: Re: [PANIC] ohci1394 & copy large files Message-Id: <20040404162818.1caa25a9.rddunlap@osdl.org> In-Reply-To: <20040404231746.GX13168@phunnypharm.org> References: <20040404141600.GB10378@ds9.ch> <20040404141339.GW13168@phunnypharm.org> <1081119623.1285.121.camel@gaston> <20040404231746.GX13168@phunnypharm.org> Organization: OSDL X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1775 Lines: 38 On Sun, 4 Apr 2004 19:17:46 -0400 Ben Collins wrote: | On Mon, Apr 05, 2004 at 09:00:24AM +1000, Benjamin Herrenschmidt wrote: | > On Mon, 2004-04-05 at 00:13, Ben Collins wrote: | > > On Sun, Apr 04, 2004 at 04:16:00PM +0200, Marcel Lanz wrote: | > > > Since 2.6.4 and still in 2.6.5 I get regurarly a Kernel panic if I try | > > > to backup large files (10-35GB) to an external attached disc (200GB/JFS) via ieee1394/sbp2. | > > > | > > > Has anyone similar problems ? | > > | > > Known issue, fixed in our repo. I still need to sync with Linus once I | > > iron one more issue and merge some more patches. | > | > Hi Ben ! | > | > I don't want to be too critical or harsh or whatever, but why don't you | > just send such fixes right upstream instead of stacking patches for a | > while in your repo ? From my experience, such "batching" of patches is | > the _wrong_ thing to do, and typically, there is a major useability | > issue with sbp2 that could have been "right" in 2.6.5 final and will not | > be (so we'll have to wait what ? 1 or 2 monthes more now to have a | > release kernel with a reliable sbp2) | | Because the fix was pretty extensive and needed testing. It was | potentially more broken that the problem it was fixing. Sending untested | patches to Linus is far worse than batching a few up and pushing to him. Was (is) it already being tested more extensively in the -mm patches before going to Linus? Should/could be. E.g., that's what gregkh does, and ACPI, etc. -- ~Randy - 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/