Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754601AbYBHWR5 (ORCPT ); Fri, 8 Feb 2008 17:17:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751191AbYBHWRu (ORCPT ); Fri, 8 Feb 2008 17:17:50 -0500 Received: from mail.windriver.com ([147.11.1.11]:41913 "EHLO mail.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbYBHWRt (ORCPT ); Fri, 8 Feb 2008 17:17:49 -0500 Message-ID: <47ACD4CB.7090701@windriver.com> Date: Fri, 08 Feb 2008 16:16:43 -0600 From: Jason Wessel User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Linus Torvalds CC: Jan Kiszka , Andi Kleen , Maxim Levitsky , Ingo Molnar , linux-kernel@vger.kernel.org, Andrew Morton , Thomas Gleixner , "H. Peter Anvin" Subject: Re: [RFC][PATCH] KGDB: remove kgdb-own fault handling References: <20080130011550.GA31853@elte.hu> <200802050436.31070.maximlevitsky@gmail.com> <47AC95FC.5090701@siemens.com> <20080208185719.GA11573@one.firstfloor.org> <47ACC97C.3000806@web.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Feb 2008 22:16:22.0215 (UTC) FILETIME=[3C7C4D70:01C86AA0] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1363 Lines: 41 Linus Torvalds wrote: > On Fri, 8 Feb 2008, Jan Kiszka wrote: > >> Well, let's try it this way: Find below a patch against kgdb.git that >> removes the special fault handling (this wouldn't be the first feature I >> recently removed from kgdb :->). Light testing revealed no obvious >> problems yet. >> > > That is indeed horrible code. No way will I merge anything that has things > like that even in it's *history* (ie somebody needs to re-generate the > tree without code like that - some things should not be allowed to exist). > > I concur. I will collapse the entire kgdb tree back to the original few patches which can be bisected. > That said, while just using "probe_kernel_addr()" is certainly much > better, it's still really inefficient. If you actually want to do a "safe > memory copy", then the right way to do that is basically to do > > pagefault_disable(); > leftover = __copy_from_user_inatomic(dst, src, count); > pagefault_enable(); > > if (leftover) > handle_the_fact_that_the_copy_didnt_complete(); > > Duly Noted. Further cleanups are in progress. Thanks, Jason. -- 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/