Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Feb 2001 20:26:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Feb 2001 20:26:23 -0500 Received: from neon-gw.transmeta.com ([209.10.217.66]:9992 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 6 Feb 2001 20:26:17 -0500 Date: Tue, 6 Feb 2001 17:26:02 -0800 (PST) From: Linus Torvalds To: Ingo Molnar cc: "Jeff V. Merkey" , Jens Axboe , "Stephen C. Tweedie" , Ben LaHaise , Alan Cox , Manfred Spraul , Steve Lord , Linux Kernel List , kiobuf-io-devel@lists.sourceforge.net Subject: Re: [Kiobuf-io-devel] RFC: Kernel mechanism: Compound event wait In-Reply-To: Message-ID: 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 On Wed, 7 Feb 2001, Ingo Molnar wrote: > > most likely some coding error on your side. buffer-size mismatches should > show up as filesystem corruption or random DMA scribble, not in-driver > oopses. I'm not sure. If I was a driver writer (and I'm happy those days are mostly behind me ;), I would not be totally dis-inclined to check for various limits and things. There can be hardware out there that simply has trouble with non-native alignment, ie be unhappy about getting a 1kB request that is aligned in memory at a 512-byte boundary. So there are real reasons why drivers might need updating. Don't dismiss the concerns out-of-hand. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/