linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
	Alan Tull <atull@kernel.org>,
	linux-fpga@vger.kernel.org,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Moritz Fischer <mdf@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 15/16] of: unittest: initialize args before calling of_irq_parse_one()
Date: Fri, 5 Oct 2018 12:04:26 -0700	[thread overview]
Message-ID: <d251f99e-6618-f1d2-814f-7aaffb8f499f@gmail.com> (raw)
In-Reply-To: <CAL_Jsq+dqRr54_WAdBQ88sJytAuLL=U9kF_Xbj5rJv4PVn9gQg@mail.gmail.com>

On 10/05/18 07:53, Rob Herring wrote:
> On Thu, Oct 4, 2018 at 11:14 PM <frowand.list@gmail.com> wrote:
>>
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> Callers of of_irq_parse_one() blindly use the pointer args.np
>> without checking whether of_irq_parse_one() had an error and
>> thus did not set the value of args.np.  Initialize args to
>> zero so that using the format "%pOF" to show the value of
>> args.np will show "(null)" when of_irq_parse_one() has an
>> error and does not set args.np instead of trying to
>> dereference a random value.
>>
>> Reported-by: Guenter Roeck <linux@roeck-us.net>
>> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
>> ---
>>  drivers/of/unittest.c | 5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> Does this need to be part of this series?

I do not know if it could be independently applied before the
rest of the series (I have not tested that).  I included it
in the series because the series has so many other changes to
unittest.c.

If you want me to break this out, I will remove it from this
series and resend it after the rest of the series has been
pulled to mainline (and rebase on the new mainline).

This patch is not fixing a known failure case - the current
test data does not trigger the problem.  The recent patch
from  Guenter that you already accepted fixes the known failure
case, so this patch is not urgent.  The same is true about the
other cases Guenter pointed out that this patch should fix.

-Frank

  reply	other threads:[~2018-10-05 19:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  4:12 [PATCH 00/16] of: overlay: validation checks, subsequent fixes frowand.list
2018-10-05  4:12 ` [PATCH 01/16] of: overlay: add tests to validate kfrees from overlay removal frowand.list
2018-10-05  4:12 ` [PATCH 02/16] of: overlay: add missing of_node_put() after add new node to changeset frowand.list
2018-10-05  4:12 ` [PATCH 03/16] of: overlay: add missing of_node_get() in __of_attach_node_sysfs frowand.list
2018-10-05  4:12 ` [PATCH 04/16] powerpc/pseries: add of_node_put() in dlpar_detach_node() frowand.list
2018-10-05  4:12 ` [PATCH 05/16] of: overlay: use prop add changeset entry for property in new nodes frowand.list
2018-10-09 20:28   ` Alan Tull
2018-10-09 23:44     ` Frank Rowand
2018-10-10  6:04     ` [PATCH 05.1/16] of:overlay: missing name, phandle, linux, phandle " frowand.list
2018-10-10  6:49       ` Frank Rowand
2018-10-10 20:40         ` Alan Tull
2018-10-10 21:03           ` Frank Rowand
2018-10-11  5:39             ` Frank Rowand
2018-10-11 19:33               ` Alan Tull
2018-10-11 23:38                 ` Frank Rowand
2018-10-05  4:12 ` [PATCH 06/16] of: overlay: do not duplicate properties from overlay for " frowand.list
2018-10-05  4:12 ` [PATCH 07/16] of: dynamic: change type of of_{at, de}tach_node() to void frowand.list
2018-10-05  4:12 ` [PATCH 08/16] of: overlay: reorder fields in struct fragment frowand.list
2018-10-05  4:12 ` [PATCH 09/16] of: overlay: validate overlay properties #address-cells and #size-cells frowand.list
2018-10-05 15:07   ` Rob Herring
2018-10-05 18:53     ` Frank Rowand
2018-10-05 19:04       ` Rob Herring
2018-10-05 19:09         ` Frank Rowand
2018-10-08 15:57   ` Alan Tull
2018-10-08 18:46     ` Alan Tull
2018-10-09  0:02       ` Frank Rowand
2018-10-09 18:40         ` Alan Tull
2018-10-05  4:12 ` [PATCH 10/16] of: overlay: make all pr_debug() and pr_err() messages unique frowand.list
2018-10-05  4:12 ` [PATCH 11/16] of: overlay: test case of two fragments adding same node frowand.list
2018-10-05  4:12 ` [PATCH 12/16] of: overlay: check prevents multiple fragments add or delete " frowand.list
2018-10-05  4:12 ` [PATCH 13/16] of: overlay: check prevents multiple fragments touching same property frowand.list
2018-10-05  4:12 ` [PATCH 14/16] of: unittest: remove unused of_unittest_apply_overlay() argument frowand.list
2018-10-05  4:12 ` [PATCH 15/16] of: unittest: initialize args before calling of_irq_parse_one() frowand.list
2018-10-05 13:26   ` Guenter Roeck
2018-10-05 19:05     ` Frank Rowand
2018-10-05 14:53   ` Rob Herring
2018-10-05 19:04     ` Frank Rowand [this message]
2018-10-05  4:12 ` [PATCH 16/16] of: unittest: find overlays[] entry by name instead of index frowand.list

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=d251f99e-6618-f1d2-814f-7aaffb8f499f@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=atull@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mdf@kernel.org \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=paulus@samba.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).