linux-kernel - Re: [RFC] Second OLPC Viafb series, v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100501165759.720dfade@bike.lwn.net>
Date:	Sat, 1 May 2010 16:57:59 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Florian Tobias Schandinat <FlorianSchandinat@....de>
Cc:	linux-kernel@...r.kernel.org, Harald Welte <laforge@...monks.org>,
	linux-fbdev@...r.kernel.org, JosephChan@....com.tw,
	ScottFang@...tech.com.cn
Subject: Re: [RFC] Second OLPC Viafb series, v2

On Sat, 01 May 2010 23:28:55 +0200
Florian Tobias Schandinat <FlorianSchandinat@....de> wrote:

> The only information I can supply so far is that it happened already 
> while unregistering the first platform. The registration of it seemed to 
> be successful. I did not yet dig deep enough into the subsystem to find 
> the bug. Any ideas?

Yes, I think I know what's going on.  Platform devices call kfree() on
platform_data at release time.  That's a little aspect of the API that
I had overlooked...  suffice to say, I'd not set platform_data to
something that kfree() was expecting to see.

Best solution, probably, is to just set it to NULL prior to
unregistering the device.  Will do something along those lines shortly.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/