Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755948AbYLaEJA (ORCPT ); Tue, 30 Dec 2008 23:09:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751530AbYLaEIv (ORCPT ); Tue, 30 Dec 2008 23:08:51 -0500 Received: from ozlabs.org ([203.10.76.45]:54305 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbYLaEIu (ORCPT ); Tue, 30 Dec 2008 23:08:50 -0500 From: Rusty Russell To: Helge Deller Subject: Re: [PATCH] parisc: fix module loading failure of large kernel modules (take 2) Date: Wed, 31 Dec 2008 14:38:34 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) Cc: "linux-parisc" , Linux Kernel Development , Kyle McMartin , Randolph Chung , Linus , Andrew Morton , Sam Ravnborg , John David Anglin References: <4959346E.7060600@gmx.de> <200812310915.41693.rusty@rustcorp.com.au> <495AA891.2030104@gmx.de> In-Reply-To: <495AA891.2030104@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812311438.35394.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 813 Lines: 18 On Wednesday 31 December 2008 09:32:41 Helge Deller wrote: > BTW, although the comment states that arches can change section sizes > in the module_frob_arch_sections() function: > /* Allow arches to frob section contents and sizes. */ > it will break horrible if you do so. > What I found was, that if you change sh_size, at least the module > references / dependency chain will break when running lsmod. Well, you can change the size of NOBITS sections: other things are likely to be less successful. You could probably make them smaller, though. Cheers, Rusty. -- 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/