| 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: <20140107214119.GG3231@htj.dyndns.org> Date: Tue, 7 Jan 2014 16:41:19 -0500 From: Tejun Heo <tj@...nel.org> To: gregkh@...uxfoundation.org Cc: linux-kernel@...r.kernel.org, schwidefsky@...ibm.com, heiko.carstens@...ibm.com, stern@...land.harvard.edu, JBottomley@...allels.com, bhelgaas@...gle.com Subject: Re: [PATCHSET driver-core-next] kernfs, sysfs, driver-core: implement synchronous self-removal On Tue, Jan 07, 2014 at 12:59:38PM -0500, Tejun Heo wrote: > This patchset improves kernfs removal path and implements > kernfs_remove_self() which is to be called from an on-going kernfs > operation and removes the self node. The function can be called > concurrently and only one will return %true and all others will wait > until the winner's file operation is complete (not the > kernfs_remove_self() call itself but the enclosing file operation > which invoked the function). This ensures that if there are multiple > concurrent "echo 1 > asdf/delete", all of them would finish only after > the whole store_delete() method is complete. Heh, dang it. Please ignore this posting. I thought I could get away with this but apparently cgroup would need something a bit more flexible. :( I'll post an updated version later. Thanks. -- tejun -- 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