All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liang He" <windhl@126.com>
To: Conor.Dooley@microchip.com
Cc: christophe.leroy@csgroup.eu, oss@buserror.net,
	mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v4] powerpc:85xx: Add missing of_node_put() in sgy_cst1000
Date: Fri, 17 Jun 2022 16:34:56 +0800 (CST)	[thread overview]
Message-ID: <4be090c8.607e.18170cd11ad.Coremail.windhl@126.com> (raw)
In-Reply-To: <33668b61-4ae7-f625-0eb3-e15d2119623c@microchip.com>


At 2022-06-17 16:27:03, Conor.Dooley@microchip.com wrote:
>On 17/06/2022 09:17, Liang He wrote:
>> 
>> 
>> 
>> At 2022-06-17 14:53:13, "Christophe Leroy" <christophe.leroy@csgroup.eu> wrote:
>>>
>>>
>>> Le 17/06/2022 à 08:45, Liang He a écrit :
>>>>
>>>>
>>>>
>>>> At 2022-06-17 14:28:56, "Christophe Leroy" <christophe.leroy@csgroup.eu> wrote:
>>>>>
>>>>>
>>>>> Le 17/06/2022 à 08:08, Liang He a écrit :
>>>>>> In gpio_halt_probe(), of_find_matching_node() will return a node
>>>>>> pointer with refcount incremented. We should use of_node_put() in
>>>>>> fail path or when it is not used anymore.
>>>>>>
>>>>>> Signed-off-by: Liang He <windhl@126.com>
>>>>>> ---
>>>>>>     changelog:
>>>>>>     v4: reuse exist 'err' and use a simple code style, advised by CJ
>>>>>>     v3: use local 'child_node' advised by Michael.
>>>>>>     v2: use goto-label patch style advised by Christophe Leroy.
>>>>>>     v1: add of_node_put() before each exit.
>>>>>>
>>>>>>     arch/powerpc/platforms/85xx/sgy_cts1000.c | 35 ++++++++++++++---------
>>>>>>     1 file changed, 22 insertions(+), 13 deletions(-)
>>>>>>
>>>>>> diff --git a/arch/powerpc/platforms/85xx/sgy_cts1000.c b/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> index 98ae64075193..e4588943fe7e 100644
>>>>>> --- a/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> +++ b/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> @@ -71,6 +71,7 @@ static int gpio_halt_probe(struct platform_device *pdev)
>>>>>>     {
>>>>>>     	enum of_gpio_flags flags;
>>>>>>     	struct device_node *node = pdev->dev.of_node;
>>>>>> +	struct device_node *child_node;
>>>>>>     	int gpio, err, irq;
>>>>>>     	int trigger;
>>>>>>     
>>>>>> @@ -78,26 +79,29 @@ static int gpio_halt_probe(struct platform_device *pdev)
>>>>>>     		return -ENODEV;
>>>>>>     
>>>>>>     	/* If there's no matching child, this isn't really an error */
>>>>>> -	halt_node = of_find_matching_node(node, child_match);
>>>>>> -	if (!halt_node)
>>>>>> +	child_node = of_find_matching_node(node, child_match);
>>>>>> +	if (!child_node)
>>>>>>     		return 0;
>>>>>>     
>>>>>>     	/* Technically we could just read the first one, but punish
>>>>>>     	 * DT writers for invalid form. */
>>>>>> -	if (of_gpio_count(halt_node) != 1)
>>>>>> -		return -EINVAL;
>>>>>> +	if (of_gpio_count(child_node) != 1) {
>>>>>> +		err = -EINVAL;
>>>>>> +		goto err_put;
>>>>>> +	}
>>>>>>     
>>>>>>     	/* Get the gpio number relative to the dynamic base. */
>>>>>> -	gpio = of_get_gpio_flags(halt_node, 0, &flags);
>>>>>> -	if (!gpio_is_valid(gpio))
>>>>>> -		return -EINVAL;
>>>>>> +	gpio = of_get_gpio_flags(child_node, 0, &flags);
>>>>>> +	if (!gpio_is_valid(gpio)) {
>>>>>> +		err = -EINVAL;
>>>>>> +		gotot err_put;
>>>>>
>>>>> Did you test the build ?
>>>>
>>>> Sorry for this fault.
>>>>
>>>> In fact, I am still finding an efficient way to building different arch source code as I only have x86-64.
>>>>
>>>> Now I am try using QEMU.
>>>>
>>>> Anyway, sorry for this fault.
>>>
>>> You can find cross compilers for most architectures for x86-64 here :
>>> https://mirrors.edge.kernel.org/pub/tools/crosstool/
>>>
>>> Christophe
>> 
>> Hi, Christophe and Conor.
>> 
>> Sorry to trouble you again.
>> 
>> Now I only know how to quickly identify the refcounting bugs, but I cannot efficiently give a build test.
>> 
>> For example, I use the cross compilers 'powerpc-linux-gnu-gcc' to compile 'arch/powerpc/platforms/85xx/sgy_cts1000.c' with -fsyntax-only flag.
>> But I meet too many header file missing errors. Even if I add some 'include' pathes, e.g., ./arch/powerpc/include, ./include,
>> there are still too many other errors.
>> 
>> So if there is any efficient way to check my patch code to avoid 'gotot' error again.
>
>idk anything about powerpc, but what I find is a nice way to get a compiler
>for an arch I don't use is to search on lore.kernel.org for a 0day robot
>build error since it gives instructions for building on that arch.
>For example:
>https://lore.kernel.org/linuxppc-dev/202206060910.rYNTFqdI-lkp@intel.com/
>
>
>In this case, your bug seems obvious? You typed "gotot" instead of "goto".
>
>Hope that helps,
>Conor.
>
>> 
>> Thanks again, Christophe and Conor.
>> 
>> Liang


Thanks so much, I will try it.

WARNING: multiple messages have this Message-ID (diff)
From: "Liang He" <windhl@126.com>
To: Conor.Dooley@microchip.com
Cc: linux-kernel@vger.kernel.org, oss@buserror.net, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re:Re: [PATCH v4] powerpc:85xx: Add missing of_node_put() in sgy_cst1000
Date: Fri, 17 Jun 2022 16:34:56 +0800 (CST)	[thread overview]
Message-ID: <4be090c8.607e.18170cd11ad.Coremail.windhl@126.com> (raw)
In-Reply-To: <33668b61-4ae7-f625-0eb3-e15d2119623c@microchip.com>


At 2022-06-17 16:27:03, Conor.Dooley@microchip.com wrote:
>On 17/06/2022 09:17, Liang He wrote:
>> 
>> 
>> 
>> At 2022-06-17 14:53:13, "Christophe Leroy" <christophe.leroy@csgroup.eu> wrote:
>>>
>>>
>>> Le 17/06/2022 à 08:45, Liang He a écrit :
>>>>
>>>>
>>>>
>>>> At 2022-06-17 14:28:56, "Christophe Leroy" <christophe.leroy@csgroup.eu> wrote:
>>>>>
>>>>>
>>>>> Le 17/06/2022 à 08:08, Liang He a écrit :
>>>>>> In gpio_halt_probe(), of_find_matching_node() will return a node
>>>>>> pointer with refcount incremented. We should use of_node_put() in
>>>>>> fail path or when it is not used anymore.
>>>>>>
>>>>>> Signed-off-by: Liang He <windhl@126.com>
>>>>>> ---
>>>>>>     changelog:
>>>>>>     v4: reuse exist 'err' and use a simple code style, advised by CJ
>>>>>>     v3: use local 'child_node' advised by Michael.
>>>>>>     v2: use goto-label patch style advised by Christophe Leroy.
>>>>>>     v1: add of_node_put() before each exit.
>>>>>>
>>>>>>     arch/powerpc/platforms/85xx/sgy_cts1000.c | 35 ++++++++++++++---------
>>>>>>     1 file changed, 22 insertions(+), 13 deletions(-)
>>>>>>
>>>>>> diff --git a/arch/powerpc/platforms/85xx/sgy_cts1000.c b/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> index 98ae64075193..e4588943fe7e 100644
>>>>>> --- a/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> +++ b/arch/powerpc/platforms/85xx/sgy_cts1000.c
>>>>>> @@ -71,6 +71,7 @@ static int gpio_halt_probe(struct platform_device *pdev)
>>>>>>     {
>>>>>>     	enum of_gpio_flags flags;
>>>>>>     	struct device_node *node = pdev->dev.of_node;
>>>>>> +	struct device_node *child_node;
>>>>>>     	int gpio, err, irq;
>>>>>>     	int trigger;
>>>>>>     
>>>>>> @@ -78,26 +79,29 @@ static int gpio_halt_probe(struct platform_device *pdev)
>>>>>>     		return -ENODEV;
>>>>>>     
>>>>>>     	/* If there's no matching child, this isn't really an error */
>>>>>> -	halt_node = of_find_matching_node(node, child_match);
>>>>>> -	if (!halt_node)
>>>>>> +	child_node = of_find_matching_node(node, child_match);
>>>>>> +	if (!child_node)
>>>>>>     		return 0;
>>>>>>     
>>>>>>     	/* Technically we could just read the first one, but punish
>>>>>>     	 * DT writers for invalid form. */
>>>>>> -	if (of_gpio_count(halt_node) != 1)
>>>>>> -		return -EINVAL;
>>>>>> +	if (of_gpio_count(child_node) != 1) {
>>>>>> +		err = -EINVAL;
>>>>>> +		goto err_put;
>>>>>> +	}
>>>>>>     
>>>>>>     	/* Get the gpio number relative to the dynamic base. */
>>>>>> -	gpio = of_get_gpio_flags(halt_node, 0, &flags);
>>>>>> -	if (!gpio_is_valid(gpio))
>>>>>> -		return -EINVAL;
>>>>>> +	gpio = of_get_gpio_flags(child_node, 0, &flags);
>>>>>> +	if (!gpio_is_valid(gpio)) {
>>>>>> +		err = -EINVAL;
>>>>>> +		gotot err_put;
>>>>>
>>>>> Did you test the build ?
>>>>
>>>> Sorry for this fault.
>>>>
>>>> In fact, I am still finding an efficient way to building different arch source code as I only have x86-64.
>>>>
>>>> Now I am try using QEMU.
>>>>
>>>> Anyway, sorry for this fault.
>>>
>>> You can find cross compilers for most architectures for x86-64 here :
>>> https://mirrors.edge.kernel.org/pub/tools/crosstool/
>>>
>>> Christophe
>> 
>> Hi, Christophe and Conor.
>> 
>> Sorry to trouble you again.
>> 
>> Now I only know how to quickly identify the refcounting bugs, but I cannot efficiently give a build test.
>> 
>> For example, I use the cross compilers 'powerpc-linux-gnu-gcc' to compile 'arch/powerpc/platforms/85xx/sgy_cts1000.c' with -fsyntax-only flag.
>> But I meet too many header file missing errors. Even if I add some 'include' pathes, e.g., ./arch/powerpc/include, ./include,
>> there are still too many other errors.
>> 
>> So if there is any efficient way to check my patch code to avoid 'gotot' error again.
>
>idk anything about powerpc, but what I find is a nice way to get a compiler
>for an arch I don't use is to search on lore.kernel.org for a 0day robot
>build error since it gives instructions for building on that arch.
>For example:
>https://lore.kernel.org/linuxppc-dev/202206060910.rYNTFqdI-lkp@intel.com/
>
>
>In this case, your bug seems obvious? You typed "gotot" instead of "goto".
>
>Hope that helps,
>Conor.
>
>> 
>> Thanks again, Christophe and Conor.
>> 
>> Liang


Thanks so much, I will try it.

  reply	other threads:[~2022-06-17  8:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  6:08 [PATCH v4] powerpc:85xx: Add missing of_node_put() in sgy_cst1000 Liang He
2022-06-17  6:08 ` Liang He
2022-06-17  6:28 ` Christophe Leroy
2022-06-17  6:45   ` Liang He
2022-06-17  6:45     ` Liang He
2022-06-17  6:53     ` Christophe Leroy
2022-06-17  6:53       ` Christophe Leroy
2022-06-17  8:17       ` Liang He
2022-06-17  8:17         ` Liang He
2022-06-17  8:27         ` Conor.Dooley
2022-06-17  8:27           ` Conor.Dooley
2022-06-17  8:34           ` Liang He [this message]
2022-06-17  8:34             ` Liang He
2022-06-17 10:47           ` Liang He
2022-06-17 10:47             ` Liang He
2022-06-17 10:57             ` Christophe Leroy
2022-06-17 10:57               ` Christophe Leroy
2022-06-17 11:46               ` Liang He
2022-06-17 11:46                 ` Liang He

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=4be090c8.607e.18170cd11ad.Coremail.windhl@126.com \
    --to=windhl@126.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oss@buserror.net \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.