| 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: <ffc2b1d40911250127x7b3c3609qb99820d212a7a0ad@mail.gmail.com> Date: Wed, 25 Nov 2009 11:27:58 +0200 From: eran liberty <eran.liberty@...il.com> To: gregkh@...e.de, balajirrao@...il.com Cc: linux-kernel@...r.kernel.org Subject: kobjects: mark cleaned up kobjects as unitialized Hi Greg & Balaji, After diving into the LDKM and failed to spot the point where you actually un-initialize the 'state_initialized' of a kobject... and since I have statically allocated object which trip over this very same trap... Google-ing for others who fell into this trap, I found your thread/patch at: http://lkml.org/lkml/2008/3/8/155 and http://lkml.indiana.edu/hypermail/linux/kernel/0902.0/01969.html I noticed this patch did not make it into the mainline. Is this patch still valid? Is there some other, better way to do it by the book? Right now I by-pass the problem by memset-ing the whole object after I release it... but I feel this is a bit brutal. -- Liberty -- 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