linux-kernel - Re: 2.6.21-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070506135531.85417c86.akpm@linux-foundation.org>
Date:	Sun, 6 May 2007 13:55:31 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Dan Kruchinin <dubalom@...il.com>, linux-kernel@...r.kernel.org,
	Dan Williams <dan.j.williams@...el.com>
Subject: Re: 2.6.21-mm1

On Sun, 6 May 2007 22:44:29 +0200 Sam Ravnborg <sam@...nborg.org> wrote:

> On Sun, May 06, 2007 at 08:33:48AM +0400, Dan Kruchinin wrote:
> > > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/
> > 
> > I have the following message after kernel compilation:
> > 
> > ---
> > ...
> > WARNING: init/built-in.o - Section mismatch: reference to .init.text:
> > from .text between 'rest_init' (at offset 0x11e) and 'try_name'
> 
> Covered in another mail.
> 
> > ...
> > ...
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x20)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x24)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x28)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x2c)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x30)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x34)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x38)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x3c)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x40)
> > WARNING: drivers/dma/async_tx.o - Section mismatch: reference to
> > .init.data: from .data after 'channel_table' (at offset 0x44)
> 
> We have following code:
> /* guarantee that calls that happen before init will not find a channel */
> static struct chan_ref_percpu __initdata null_chan_ref[NR_CPUS];
> 
> static struct chan_ref_percpu *channel_table[] = {
> 	DMA_TX_ARRAY_INIT(null_chan_ref)
> };
> 
> The DMA_TX_ARRAY_INIT is some macro obscufation that serves no
> real use and just hide a few assignements.
> What happens here is that we assign channel_table a value
> that are used as cover-up until the real assignment happens
> in the init function.
> So the only real way to fix this seems to remove the otherwise correct
> __initdata mark on null_chan_ref.
> Thats one pointer wasted pr. cpu (in total NR_CPUS).
> 

(add Dan to cc)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/