| 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: <20070710125012.17dcba32@gondolin.boeblingen.de.ibm.com> Date: Tue, 10 Jul 2007 12:50:12 +0200 From: Cornelia Huck <cornelia.huck@...ibm.com> To: Tejun Heo <htejun@...il.com> Cc: Alan Stern <stern@...land.harvard.edu>, Kernel development list <linux-kernel@...r.kernel.org> Subject: Re: Sysfs and suicidal attributes On Tue, 10 Jul 2007 18:13:43 +0900, Tejun Heo <htejun@...il.com> wrote: > More like "device unregistering itself from its attribute" vs. "whatever > else". Ah, ok. I don't think we can make those the same, but "trigger an action and return" vs. "whatever else" may be possible. > > >>> A general immediate disconnect of the buffers (which will be handled in > >>> a second pass) would be great, but doesn't sound easy. > >> I haven't thought too hard about actual implementation but it's pretty > >> specific case. If doing things in generic manner is difficult, there > >> are plenty of shortcuts to choose from, I think. > > > > The "second pass" approach where the store method calls the sysfs core > > or sets a flag or whatever sounds doable, but I'm not sure how general > > we can get. Maybe for all store methods that just trigger an action. > > Hmm... I'll give it a shot in a few days. Cool. I'd try myself, but I'm currently a bit short on time :) - 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