[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVhL+5y9n7n8JkPMwdTd-N14rcOc7Sm_5WHN+w8nVg-4Q@mail.gmail.com>
Date: Mon, 25 Jun 2012 15:55:12 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Ingo Molnar <mingo@...nel.org>, lenb@...nel.org, x86@...nel.org,
Ulrich Drepper <drepper@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-pci@...r.kernel.org
Subject: Re: [PATCH] PCI, X86: busnum/node boot command line for pci dev node setting.
On Mon, Jun 25, 2012 at 3:38 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Mon, Jun 25, 2012 at 1:59 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>>
>> Can you convince me this is safe? pci_setup() is an early_param, so
>> it looks to me like we might be saving a pointer to initdata in this
>> call path:
>>
>> setup_arch
>> parse_early_param
>> strlcpy(tmp_cmdline, boot_command_line)
>> parse_early_options(__initdata tmp_cmdline)
>> parse_args
>> do_early_param
>> ...
>> pci_setup (early_param)
>> pcibios_setup
>> remember_busnum_node
>>
>> And then we use that saved pointer to parse the string at host bridge
>> add-time, which might be after initdata has been freed.
>
> ok, that will need one separate buffer.
could used saved_command_line directly.
also do we need to include this one to upsteam ?
Thanks
Yinghai
Download attachment "busnum_node_v3_x.patch" of type "application/octet-stream" (4021 bytes)
Powered by blists - more mailing lists