From: Yuan Can <yuancan@huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <bhelgaas@google.com>, <gregkh@suse.de>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: cpqphp: Fix error handling in cpqhpc_init()
Date: Wed, 23 Nov 2022 10:18:29 +0800 [thread overview]
Message-ID: <92523fb0-0df4-e0f9-d7ee-16e3c4cdc6ed@huawei.com> (raw)
In-Reply-To: <20221122200551.GA212321@bhelgaas>
在 2022/11/23 4:05, Bjorn Helgaas 写道:
> On Tue, Nov 22, 2022 at 10:13:46AM +0000, Yuan Can wrote:
>> The cpqhpc_init() returns the result of pci_register_driver() without
>> checking it, if pci_register_driver() failed, the debugfs created in
>> cpqhp_initialize_debugfs() is not removed, resulting the debugfs of
>> cpqhp can never be created later.
>> Fix by calling cpqhp_shutdown_debugfs() when pci_register_driver() failed.
> Add a blank line between paragraphs.
Ok.
>> Fixes: 9f3f4681291f ("[PATCH] PCI Hotplug: fix up the sysfs file in the compaq pci hotplug driver")
>> Signed-off-by: Yuan Can <yuancan@huawei.com>
>> ---
>> drivers/pci/hotplug/cpqphp_core.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/pci/hotplug/cpqphp_core.c b/drivers/pci/hotplug/cpqphp_core.c
>> index c94b40e64baf..c47981ef92ea 100644
>> --- a/drivers/pci/hotplug/cpqphp_core.c
>> +++ b/drivers/pci/hotplug/cpqphp_core.c
>> @@ -1389,6 +1389,8 @@ static int __init cpqhpc_init(void)
>> info(DRIVER_DESC " version: " DRIVER_VERSION "\n");
>> cpqhp_initialize_debugfs();
>> result = pci_register_driver(&cpqhpc_driver);
>> + if (result)
>> + cpqhp_shutdown_debugfs();
> Is there some reason cpqhp_initialize_debugfs() needs to be called
> before pci_register_driver()?
>
> In other words, could we do this instead?
>
> result = pci_register_driver(&cpqhpc_driver);
> if (result)
> return result;
>
> cpqhp_initialize_debugfs();
> return 0;
Thanks for the suggestion! I do not see any reason that the order must
be kept, will change to this style in the next version.
> I assume this was found by code inspection? I've never heard of
> anybody actually using this driver :)
Yes, you are right :)
>> dbg("pci_register_driver = %d\n", result);
>> return result;
>> }
>> --
>> 2.17.1
>>
--
Best regards,
Yuan Can
next prev parent reply other threads:[~2022-11-23 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 10:13 [PATCH] PCI: cpqphp: Fix error handling in cpqhpc_init() Yuan Can
2022-11-22 20:05 ` Bjorn Helgaas
2022-11-23 2:18 ` Yuan Can [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 9:29 Yuan Can
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=92523fb0-0df4-e0f9-d7ee-16e3c4cdc6ed@huawei.com \
--to=yuancan@huawei.com \
--cc=bhelgaas@google.com \
--cc=gregkh@suse.de \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
/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