Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]

[Adrian Bunk <bunk@kernel.org>]

On Sun, Nov 11, 2007 at 03:03:56PM +0000, David Howells wrote:
> Adrian Bunk <bunk@kernel.org> wrote:
> 
> > It's BTW not an improvement that you do not only rename them but change 
> > such big functions to static inline functions in header files.
> 
> I'm not sure what you meant by that.
> 
> Renaming them indicates more clearly that their only purpose is for A.OUT
> support.
> 
> Making them inline is an improvement because it compiles the code into the
> binfmt_aout module rather than the core kernel, and gives the compiler
> optimiser a chance to reduce the size of the overall code.
>  
> And the functions aren't actually all that big or complex.  They're about
> shovelling data and don't do anything clever.
>...

My thoughts go more into the direction that we have hundreds of similar 
cases where e.g. a VFS function might currently only by used by OCFS2 
and therefore be dead code for most users, and the only maintainable 
solution will be to solve these at the compiler and/or linker level.

> > Something like this.
> 
> Was that an agreement with my suggested break up, or was there something more
> meant to be there?

That was an agreement.

> > But changes to binfmt_elf.c after the merge window that might introduce 
> > regressions (e.g. you (ab)use CONFIG_BINFMT_AOUT where you might have to 
> > introduce an CONFIG_ARCH_SUPPORTS_AOUT instead) decrease your chances of 
> > being merged that late.
> 
> That was more or less what I wanted to do originally, but I was told to use
> CONFIG_BINFMT_AOUT instead - which actually proves to have two variants:-(
> 
> Perhaps I could start with the patch that you mentioned to remove AOUT
> interpreter support from binfmt_elf.  Can you point me at it or send it to me?
> That's still not sufficient, but it removes part of the changes I have to
> make.

Andi scheduled it for removal, and I don't know whether he already has a 
patch.

> > But you might be able to do something like a
> >   cp include/asm-xtensa/a.out.h include/asm-mn10300/
> > instead.
> 
> No.  That would be wrong.  MN10300 does not define an exec struct, and nor
> should it provide an asm/a.out.h header.  It does not do AOUT format.

Read the comment at the top of the xtensa header.  ;-)

For 2.6.25 a better solution is appreciated, but for 2.6.24 such a small 
dirty workaround that can't cause breakages on other architectures would 
be better.

> David

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/