All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regmap: debugfs: Fix a boot time crash with early regmap init
Date: Thu, 24 Oct 2013 15:03:07 +0300	[thread overview]
Message-ID: <52690C7B.9070908@ti.com> (raw)
In-Reply-To: <20131024091857.GG31415@sirena.org.uk>

On 10/24/2013 12:18 PM, Mark Brown wrote:
> On Thu, Oct 24, 2013 at 12:07:48PM +0300, Tero Kristo wrote:
>
>> +	if (!regmap_debugfs_root) {
>> +		struct regmap_debugfs_node *node;
>> +		node = kzalloc(sizeof(*node), GFP_KERNEL);
>> +		if (!node)
>> +			return;
>> +		node->map = map;
>> +		node->name = name;
>> +		list_add(&node->link, &regmap_debugfs_early);
>> +		return;
>> +	}
>> +
>
> init is somewhat parallel so I'd be happier if we locked the list to
> make sure that we don't corrupt the list.

Ok, I added a mutex for protection (later registration might take some 
time so didn't want to use spinlock.)

> We also need something to handle removal of items from the list if the
> regmap is destroyed prior to the initcall running (for example in error
> handling cases), otherwise we could end up creating debugfs files
> pointing at devices that no longer exist.

Added cleanup for the list in the regmap_debugfs_exit() call. Sending v2 
shortly.

-Tero

      reply	other threads:[~2013-10-24 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  9:07 [PATCH] regmap: debugfs: Fix a boot time crash with early regmap init Tero Kristo
2013-10-24  9:18 ` Mark Brown
2013-10-24 12:03   ` Tero Kristo [this message]

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=52690C7B.9070908@ti.com \
    --to=t-kristo@ti.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@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 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.