linux-kernel - Re: Fixing the main programmer thinko with the device model

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]

Date:	25 Mar 2008 10:57:32 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Greg KH <greg@...ah.com>, Kay Sievers <kay.sievers@...y.org>,
	"Van De Ven, Arjan" <arjan@...ux.intel.com>,
	Al Viro <viro@...IV.linux.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Fixing the main programmer thinko with the device model

James Bottomley <James.Bottomley@...senPartnership.com> writes:
> 
> That's true, but irrelevant (and also soon to be untrue if we get rid of
> the scsi_device class as you and Kay keep requesting).  The two calls
> release references on the actual embedded generic device, it's nothing
> to do with entangled lifetime rules.

<heretic thought>Has anybody ever considered just doing away with 
the problematic and bug prone and tricky reference counts for kobjects 
and switch to a simple garbage collector for them?

-Andi
--
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/