Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759552AbYCXRSx (ORCPT ); Mon, 24 Mar 2008 13:18:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754647AbYCXRSl (ORCPT ); Mon, 24 Mar 2008 13:18:41 -0400 Received: from mk-filter-1-a-1.mail.uk.tiscali.com ([212.74.100.52]:58991 "EHLO mk-filter-1-a-1.mail.uk.tiscali.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754390AbYCXRSk (ORCPT ); Mon, 24 Mar 2008 13:18:40 -0400 X-Trace: 682488530/mk-filter-1.mail.uk.tiscali.com/B2C/$THROTTLED-DYNAMIC/CUSTOMER-DYNAMIC-IP/81.1.89.66 X-SBRS: None X-RemoteIP: 81.1.89.66 X-IP-MAIL-FROM: adrian@newgolddream.dyndns.info X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhUHAMp+50dRAVlC/2dsb2JhbACBW6YQ Subject: Re: [PATCH] 3/3 maple: update bus driver to support Dreamcast VMU From: Adrian McMenamin To: =?ISO-8859-1?Q?J=F6rn?= Engel Cc: Paul Mundt , Greg KH , dwmw2 , LKML , MTD , linux-sh , Andrew Morton In-Reply-To: <20080324170707.GH2899@logfs.org> References: <1206207805.6324.13.camel@localhost.localdomain> <1206209786.6324.41.camel@localhost.localdomain> <20080324033344.GB15872@linux-sh.org> <20080324144647.GC2899@logfs.org> <1206371178.6283.37.camel@localhost.localdomain> <20080324152952.GF2899@logfs.org> <1206373900.6283.39.camel@localhost.localdomain> <20080324160429.GG2899@logfs.org> <20080324170707.GH2899@logfs.org> Content-Type: text/plain; charset=UTF-8 Date: Mon, 24 Mar 2008 17:18:13 +0000 Message-Id: <1206379093.7543.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1208 Lines: 33 On Mon, 2008-03-24 at 18:07 +0100, Jörn Engel wrote: > On Mon, 24 March 2008 17:04:29 +0100, Jörn Engel wrote: > > > > Then we should be fine. I'll try to beat the code into submission. > > And here go two more interesting patches. The first is removing all > locking from the mtd driver. Since the existing locking code is nearly > impossibly to verify, I'd rather have something simple and wrong than > something complicated and wrong. > > The second rearranges the list locking a bit. Previously it was > possible to touch maple_waitq or maple_sentq without holding the lock. > With my limited understanding of the driver, the second patch may > already be enough to prevent the type of corruption you've been seeing. > > Jörn > These will fail. Removing the locks just about guarantees memory corruption and maple_waitq is not the issue - it is the objects held in maple_waitq that are the issue. I have an idea though, so let me hack at it -- 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/