From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Petr Mladek <pmladek@suse.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock
Date: Wed, 2 Aug 2023 06:35:07 +0300 [thread overview]
Message-ID: <ZMnO67avEY25XzB1@smile.fi.intel.com> (raw)
In-Reply-To: <ZMnNcJ2KW1qUZUA5@smile.fi.intel.com>
On Wed, Aug 02, 2023 at 06:28:48AM +0300, Andy Shevchenko wrote:
> On Tue, Aug 01, 2023 at 03:54:45PM -0600, Rob Herring wrote:
> > While originally it was fine to format strings using "%pOF" while
> > holding devtree_lock, this now causes a deadlock. Lockdep reports:
> >
> > of_get_parent from of_fwnode_get_parent+0x18/0x24
> > ^^^^^^^^^^^^^
> > of_fwnode_get_parent from fwnode_count_parents+0xc/0x28
> > fwnode_count_parents from fwnode_full_name_string+0x18/0xac
> > fwnode_full_name_string from device_node_string+0x1a0/0x404
> > device_node_string from pointer+0x3c0/0x534
> > pointer from vsnprintf+0x248/0x36c
> > vsnprintf from vprintk_store+0x130/0x3b4
> >
> > To fix this, move the printing in __of_changeset_entry_apply() outside the
> > lock. As there's already similar printing of the same changeset actions,
> > refactor all of them to use a common action print function. This has the
> > side benefit of getting rid of some ifdefs.
...
> > v3:
> > - Add missing 'static' reported by 0-day
>
> It reported two issues (at least what I see).
...
> > + if (pr_debug("notify "))
>
> This is weird. How did you compile it?
Urgh, you need to fix dynamic debug macros to return an error code.
> > + of_changeset_action_print(action, pr->dn, pr->prop ? pr->prop->name : NULL);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-02 3:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 21:54 [PATCH 0/5] dt: changeset fixes and cleanups Rob Herring
2023-08-01 21:54 ` [PATCH 1/5] of: unittest: Fix EXPECT for parse_phandle_with_args_map() test Rob Herring
2023-08-01 21:54 ` [PATCH 2/5] of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock Rob Herring
2023-08-02 2:49 ` kernel test robot
2023-08-02 3:28 ` Andy Shevchenko
2023-08-02 3:35 ` Andy Shevchenko [this message]
2023-08-02 21:33 ` Rob Herring
2023-08-03 17:36 ` Rob Herring
2023-08-04 18:55 ` Petr Mladek
2023-08-04 20:31 ` Rob Herring
2023-08-01 21:54 ` [PATCH 3/5] of: dynamic: Fix race in getting old property when updating property Rob Herring
2023-08-01 21:54 ` [PATCH 4/5] of: dynamic: Move dead property list check into property add/update functions Rob Herring
2023-08-02 15:12 ` Andy Shevchenko
2023-08-03 20:42 ` Rob Herring
2023-08-01 21:54 ` [PATCH 5/5] of: Refactor node and property manipulation function locking Rob Herring
2023-08-02 15:14 ` Andy Shevchenko
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=ZMnO67avEY25XzB1@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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