All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "André Przywara" <andre.przywara@arm.com>
Cc: Icenowy Zheng <icenowy@aosc.xyz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Adam Borowski <kilobyte@angband.pl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349
Date: Tue, 18 Apr 2017 16:25:05 +0900	[thread overview]
Message-ID: <20170418072505.GE3899@wtj.duckdns.org> (raw)
In-Reply-To: <3cf02066-ca0e-05f4-6a3d-ebc6d5373caf@arm.com>

Hello,

On Mon, Apr 03, 2017 at 12:48:16AM +0100, André Przywara wrote:
> So I see this problem easily now - on every boot - with an unpatched
> 4.11-rc3 kernel and the (arm64) defconfig on a Pine64 or BananaPi M64.
> I enabled devres.log and see that pinctrl probes early, but apparently
> gets deferred, pretty late actually (after 43 ADDs).
> 
> Now what sticks out from the sequence (see the attached log) is that
> there are two un-matches ADDs with a devm_kmalloc of size 0:
> sun50i-a64-pinctrl 1c20800.pinctrl: DEVRES ADD ffff80007bd84200
> devm_kzalloc_release (0 bytes)
> sun50i-a64-pinctrl 1c20800.pinctrl: DEVRES ADD ffff80007bd84100
> devm_kzalloc_release (0 bytes)
> 
> While all the other ADDs have a matching REL, those two have not. I
> guess it's due to the size being 0. Does that ring a bell?

AFAICS, 0 size allocs should be fine.

> Or is due to the fact that these two ADDs are after the RELs have
> already started, so at a point where the driver is already cleaned up?

But this sounds problematic to me.  So, these zero length allocations
are happening after release of the device is initiated?  Where are
they coming from?

Thanks.

-- 
tejun

  reply	other threads:[~2017-04-18  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170315161406.smd4na25two55jjh@angband.pl>
     [not found] ` <197431489595078@web8g.yandex.ru>
2017-03-16  1:06   ` sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Greg Kroah-Hartman
2017-03-17 14:08     ` Tejun Heo
     [not found]       ` <785901489760914@web50g.yandex.ru>
2017-03-17 14:44         ` Tejun Heo
2017-03-17 16:32           ` Adam Borowski
2017-04-02 23:48           ` André Przywara
2017-04-18  7:25             ` Tejun Heo [this message]
2017-04-18  9:12               ` Andre Przywara
2017-04-28 22:03                 ` Tejun Heo
2017-04-29 21:28                   ` Adam Borowski
2017-04-29 23:34                     ` André Przywara
2017-05-01 19:22                       ` Tejun Heo
2017-04-18 10:51               ` Icenowy Zheng

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=20170418072505.GE3899@wtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=icenowy@aosc.xyz \
    --cc=kilobyte@angband.pl \
    --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.