linux-kernel - Re: [BUG] git 2.6.31-rc3'ish: "<kobject> does not have a release() function, it is broken and must be fixed."

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: <20090806205019.GA12988@rhlx01.hs-esslingen.de>
Date:	Thu, 6 Aug 2009 22:50:19 +0200
From:	Andreas Mohr <andi@...as.de>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Greg KH <gregkh@...e.de>, Andreas Mohr <andi@...as.de>,
	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au
Subject: Re: [BUG] git 2.6.31-rc3'ish: "<kobject> does not have a release()
	function, it is broken and must be fixed."

Hi,

On Thu, Aug 06, 2009 at 01:28:01PM -0700, Roland Dreier wrote:
> ie a ktype with no release method.  And indeed, the release method was
> removed in:
> 
> commit 7a6a41615bfb2f03ce797bc24104c50b42c935e5
> Author: Greg Kroah-Hartman <gregkh@...e.de>
> Date:   Sat Dec 22 21:18:25 2007 -0800
> 
>     Modules: remove unneeded release function
> 
> ie you did it yourself!
> 
> What's the deal?

Oh I'm sure it was a cunning way of deluding oneself, and the entire
global community on top of it, too! ;)
Else it must have been successful sabotage by a certain M$ collaborator
employee I'd wager :)

Many thanks for taking part in this issue, thanks to you it sounds like we're
rather close to a solution now...

Andreas Mohr
--
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/