[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1448828800.2603.17.camel@tiscali.nl>
Date: Sun, 29 Nov 2015 21:26:40 +0100
From: Paul Bolle <pebolle@...cali.nl>
To: Tilman Schmidt <tilman@...p.cc>,
Peter Hurley <peter@...leysoftware.com>,
Sasha Levin <sasha.levin@...cle.com>
Cc: isdn@...ux-pingi.de, davem@...emloft.net,
gigaset307x-common@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: gigaset: freeing an active object
On zo, 2015-11-29 at 19:47 +0100, Tilman Schmidt wrote:
> Btw I don't see a timer_list object in struct platform_device either.
> Nor in the embedded struct device.
I found two instances of struct timer_list, rather deep down struct
ser_cardstate:
struct ser_cardstate {
struct platform_device dev {
struct device dev {
struct kobject kobj {
#ifdef CONFIG_DEBUG_KOBJECT_RELEASE
struct delayed_work release {
struct timer_list timer;
};
#endif
};
struct dev_pm_info power {
#ifdef CONFIG_PM
struct timer_list suspend_timer;
#endif
};
};
};
};
(I only spotted these two and don't think there are others in the rest
of the exploded struct ser_cardstate.)
If the above is correct it would be nice to know the .config of the
kernel used by syzkaller.
Anyhow, without further details of the chain of events that triggered
this warning, I'm afraid it will be hard to determine which struct
timer_list is at the root of all this. (Ie, there's probably quite a bit
of code to wade through in order to determine that.)
Thanks,
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists