| 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
| ||
|
Message-ID: <20071127180742.GA2768@kroah.com> Date: Tue, 27 Nov 2007 10:07:42 -0800 From: Greg KH <greg@...ah.com> To: Alan Stern <stern@...land.harvard.edu> Cc: Andrew Morton <akpm@...ux-foundation.org>, kay.sievers@...y.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Kobjects: drop child->parent ref at unregistration On Tue, Nov 27, 2007 at 12:41:23PM -0500, Alan Stern wrote: > On Tue, 27 Nov 2007, Greg KH wrote: > > > For now, I'd recommend dropping it from your tree Andrew, as it might > > cause odd issues on device removal (not quite sure though...) > > But then there's the counter-argument: If the patch does cause any odd > issues to shake loose, learning about them in advance by exposing the > patch in the -mm tree would be worthwhile. > > Sounds like it's time for an executive decision... :-) Heh. I'm not ignoring the patch, and will apply it if I test it out and see that it doesn't break anything. Then I will let it bake in -mm for a while. I just don't want to rush it as this area of the kobject core is nasty and full of tricks that I always forget. Let me finish writing up this documentation on what I do remember and then I'll attack the block device patch and this one. thanks, greg k-h - 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/
Powered by blists - more mailing lists