| 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: <20080626114242.GX4392@parisc-linux.org> Date: Thu, 26 Jun 2008 05:42:42 -0600 From: Matthew Wilcox <matthew@....cx> To: xfs@....sgi.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/6] Extend completions to provide XFS object flush requirements On Thu, Jun 26, 2008 at 09:32:09PM +1000, Dave Chinner wrote: > On Thu, Jun 26, 2008 at 05:26:12AM -0600, Matthew Wilcox wrote: > > On Thu, Jun 26, 2008 at 02:41:12PM +1000, Dave Chinner wrote: > > > XFS object flushing doesn't quite match existing completion semantics. It > > > mixed exclusive access with completion. That is, we need to mark an object as > > > being flushed before flushing it to disk, and then block any other attempt to > > > flush it until the completion occurs. > > > > This sounds like mutex semantics. Why are the existing mutexes not > > appropriate for your needs? > > Different threads doing wait and complete. Then let's leave it as a semaphore. You can get rid of the sema_t if you like, but I don't think that turning completions into semaphores is a good idea (because it's confusing). -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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