From: Frank Rowand <frowand.list@gmail.com>
To: Alan Tull <atull@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
David Airlie <airlied@linux.ie>, Jyri Sarha <jsarha@ti.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 06/12] of: overlay: detect cases where device tree may become corrupt
Date: Thu, 19 Oct 2017 12:19:41 -0700 [thread overview]
Message-ID: <59E8FACD.7030208@gmail.com> (raw)
In-Reply-To: <CANk1AXR_=yKyHmTj282o89irF-2FhsmCt-dV30Z9HkeNcVVizg@mail.gmail.com>
On 10/19/17 12:04, Alan Tull wrote:
> On Tue, Oct 17, 2017 at 6:36 PM, <frowand.list@gmail.com> wrote:
>
>> static int overlay_notify(struct overlay_changeset *ovcs,
>> enum of_overlay_notify_action action)
>> {
>> @@ -86,8 +109,14 @@ static int overlay_notify(struct overlay_changeset *ovcs,
>>
>> ret = blocking_notifier_call_chain(&overlay_notify_chain,
>> action, &nd);
>> - if (ret)
>> - return notifier_to_errno(ret);
>> + if (ret == NOTIFY_STOP)
>> + return 0;
>> + if (ret) {
>> + ret = notifier_to_errno(ret);
>> + pr_err("overlay changeset %s notifier error %d, target: %pOF\n",
>> + of_overlay_action_name[action], ret, nd.target);
>> + return ret;
>> +
>
> Hi Frank,
>
> This will spew lots of "error 0" messages for every notifier that
> returns NOTIFY_OK.
>
> rmdir /sys/kernel/config/device-tree/overlays/1
> [ 131.972505] OF: overlay: overlay changeset pre-remove notifier
> error 0, target: /soc/base_fpga_region/fpga_pr_region0
> [ 131.987879] OF: overlay: overlay changeset post-remove notifier
> error 0, target: /soc/base_fpga_region/fpga_pr_region0
Thanks for finding that. I'll send a patch so that NOTIFY_OK does
not spew an error. (And overlay_notify() should also not be
returning an error in that case.)
-Frank
>
> I could change fpga-region.c to return NOTIFY_STOP if it is accepting
> the overlay, but it will still want to return NOTIFY_OK for every case
> where it doesn't have an opinion.
>
> Alan
>
>> }
>>
>> return 0;
>
next prev parent reply other threads:[~2017-10-19 19:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 23:36 [PATCH v3 00/12] of: overlay: clean up device tree overlay code frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-10-17 23:36 ` frowand.list
[not found] ` <1508283392-18252-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-17 23:36 ` [PATCH v3 01/12] of: overlay.c: Remove comments that state the obvious, to reduce clutter frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-10-17 23:36 ` frowand.list
2017-10-17 23:36 ` [PATCH v3 11/12] of: overlay: remove a dependency on device node full_name frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-10-17 23:36 ` frowand.list
2017-10-17 23:36 ` [PATCH v3 02/12] of: overlay.c: Convert comparisons to zero or NULL to logical expressions frowand.list
2017-10-17 23:36 ` [PATCH v3 03/12] of: overlay: rename identifiers to more reflect what they do frowand.list
2017-10-17 23:36 ` [PATCH v3 04/12] of: overlay: rename identifiers in dup_and_fixup_symbol_prop() frowand.list
2017-10-17 23:36 ` [PATCH v3 05/12] of: overlay: minor restructuring frowand.list
2017-10-17 23:36 ` [PATCH v3 06/12] of: overlay: detect cases where device tree may become corrupt frowand.list
2017-10-19 19:04 ` Alan Tull
2017-10-19 19:19 ` Frank Rowand [this message]
2017-10-17 23:36 ` [PATCH v3 07/12] of: overlay: expand check of whether overlay changeset can be removed frowand.list
2017-10-17 23:36 ` [PATCH v3 08/12] of: overlay: loosen overly strict phandle clash check frowand.list
2017-10-17 23:36 ` [PATCH v3 09/12] of: overlay: avoid race condition between applying multiple overlays frowand.list
2017-10-17 23:36 ` [PATCH v3 10/12] of: overlay: simplify applying symbols from an overlay frowand.list
2017-10-17 23:36 ` [PATCH v3 12/12] of: overlay: remove unneeded check for NULL kbasename() frowand.list
2017-10-18 1:49 ` [PATCH v3 00/12] of: overlay: clean up device tree overlay code Rob Herring
2017-10-18 1:49 ` Rob Herring
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=59E8FACD.7030208@gmail.com \
--to=frowand.list@gmail.com \
--cc=airlied@linux.ie \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.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 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.