mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Section mismatch contig_page_data and bootmem_node_data
Date: Wed, 20 Aug 2008 23:53:06 +0200	[thread overview]
Message-ID: <87iqtv4am5.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <20080820135551.74911cb3@lappy.seanm.ca> (Sean MacLennan's message of "Wed, 20 Aug 2008 13:55:51 -0400")

Hi,

Sean MacLennan <smaclennan@pikatech.com> writes:

> If CONFIG_NEED_MULTIPLE_NODES is *not* set, then you get a section
> mismatch in reference from the variable contig_page_data to the
> variable __initdata bootmem_node_data.
>
> The simple solution is to just remove the __initdata from
> bootmem_node_data. We could also put an ifdef around the __initdata.
>
> Signed-off-by: Sean MacLennan <smaclennan@pikatech.com>
> ---
> diff --git a/mm/bootmem.c b/mm/bootmem.c
> index e023c68..a968ae2 100644
> --- a/mm/bootmem.c
> +++ b/mm/bootmem.c
> @@ -31,7 +31,7 @@ unsigned long max_pfn;
>  unsigned long saved_max_pfn;
>  #endif
>  
> -bootmem_data_t bootmem_node_data[MAX_NUMNODES] __initdata;
> +bootmem_data_t bootmem_node_data[MAX_NUMNODES];

It is totally valid to be init data as it does not get referenced after
bootup and should therefor be freed.

The statically defined pointer from contig_page_data is the problem and
the fix should be on this end rather than worsening code to suppress a
warning.

NAK,

	Hannes

      parent reply	other threads:[~2008-08-20 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 17:55 Sean MacLennan
2008-08-20 19:05 ` Marcin Slusarz
     [not found]   ` <20080820151531.38fc1071@lappy.seanm.ca>
     [not found]     ` <87myj74azn.fsf@skyscraper.fehenstaub.lan>
2008-08-21  0:08       ` Marcin Slusarz
2008-08-21  7:06         ` Johannes Weiner
2008-08-21 20:10           ` Marcin Slusarz
2008-08-22  6:15             ` Andrew Morton
2008-08-22 13:05               ` Marcin Slusarz
2008-08-20 21:53 ` Johannes Weiner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iqtv4am5.fsf@skyscraper.fehenstaub.lan \
    --to=hannes@saeurebad.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smaclennan@pikatech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome