From: Kishon Vijay Abraham I <kishon@ti.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: kernel test robot <lkp@intel.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [bisect done] ef1433f717 [ 7.049860] BUG: unable to handle kernel NULL pointer dereference at 0000004c
Date: Wed, 27 Jun 2018 18:42:15 +0530 [thread overview]
Message-ID: <582e6414-1a06-7521-c602-1eb77f6c67ba@ti.com> (raw)
In-Reply-To: <20180627102620.GA7893@red-moon>
On Wednesday 27 June 2018 03:56 PM, Lorenzo Pieralisi wrote:
> On Tue, Jun 26, 2018 at 04:15:01PM -0500, Bjorn Helgaas wrote:
>> On Tue, Jun 26, 2018 at 09:10:07AM +0800, kernel test robot wrote:
>>>
>>> Greetings,
>>>
>>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>>
>>> commit ef1433f717a2c63747a519d86965d73ff9bd08b3
>>> Author: Kishon Vijay Abraham I <kishon@ti.com>
>>> AuthorDate: Mon Apr 2 18:59:35 2018 +0530
>>> Commit: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>>> CommitDate: Fri May 18 16:40:50 2018 +0100
>>>
>>> PCI: endpoint: Create configfs entry for each pci_epf_device_id table entry
>>>
>>> In order to be able to provide correct driver_data for pci_epf device,
>>> a separate configfs entry for each pci_epf_device_id table entry in
>>> pci_epf_driver is required.
>>>
>>> Add support to create configfs entry for each pci_epf_device_id
>>> table entry here.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>>> Tested-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
>>
>> From the .config below:
>>
>> # CONFIG_PCI_ENDPOINT_CONFIGFS is not set
>>
>> From include/linux/pci-ep-cfs.h:
>>
>> #ifdef CONFIG_PCI_ENDPOINT_CONFIGFS
>> ...
>> #else
>> static inline struct config_group *pci_ep_cfs_add_epf_group(const char *name)
>> {
>> return 0;
>> }
>>
>> From ef1433f717a2:
>>
>> + id = driver->id_table;
>> + while (id->name[0]) {
>> + group = pci_ep_cfs_add_epf_group(id->name);
>> + mutex_lock(&pci_epf_mutex);
>> + list_add_tail(&group->group_entry, &driver->epf_group);
>>
>> Obviously group == 0 and the list_add_tail() is a NULL pointer
>> dereference.
>>
>> Looks like we need either some sort of #ifdef CONFIG_PCI_ENDPOINT_CONFIGFS
>> in __pci_epf_register_driver() and pci_epf_unregister_driver(), or
>> higher-level interfaces and corresponding stubs that add/remove all
>> the IDs.
>
> Yes, probably augment pci_ep_cfs_add_epf_group() to take a driver
> pointer so that adding a group is a NOP on !CONFIG_PCI_ENDPOINT_CONFIGFS.
>
> Kishon can you please post a fix as soon as you can, thanks.
sure, I'll try to post before this week.
Thanks
Kishon
prev parent reply other threads:[~2018-06-27 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 1:10 kernel test robot
2018-06-26 21:15 ` Bjorn Helgaas
2018-06-27 10:26 ` Lorenzo Pieralisi
2018-06-27 13:12 ` Kishon Vijay Abraham I [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=582e6414-1a06-7521-c602-1eb77f6c67ba@ti.com \
--to=kishon@ti.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=lorenzo.pieralisi@arm.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
all inboxes | Powered by JetHome®