From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Wed, 28 Mar 2012 16:32:52 -0700 From: Greg KH To: Sasha Levin Cc: Tim Abbott , Rusty Russell , stable@vger.kernel.org Subject: Re: Patch Upstream: module: Remove module size limit Message-ID: <20120328233252.GA16375@kroah.com> References: <20120328220121.108CF26EF@git.kroah.org> <20120328224112.GA10691@kroah.com> <20120328230952.GA6419@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-ID: On Thu, Mar 29, 2012 at 01:22:23AM +0200, Sasha Levin wrote: > On Thu, Mar 29, 2012 at 1:09 AM, Greg KH wrote: > > On Thu, Mar 29, 2012 at 12:57:47AM +0200, Sasha Levin wrote: > >> On Thu, Mar 29, 2012 at 12:41 AM, Greg KH wrote: > >> > For the patch below, what are the "real world use cases" that would > >> > cause this to be needed in the stable kernel trees? �Is there an > >> > in-kernel module that is affected by this limitation? > >> > >> There are no in-kernel modules which are affected, the "real world" > >> scenario is debug modules generated by Ksplice. > > > > So why is this needed for the stable kernels? �This really looks like a > > feature not a bugfix to me, how about you? > > I guess it depends on whether you consider the inability to load > modules bigger than 64mb as a bug or not. As there is no in-kernel user with this problem, no, I don't think it's a bug that meets the rules documented in Documentation/stable_kernel_rules.txt, do you? So I'll drop it, sorry. greg k-h