| 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: <1234195539.5447.2.camel@think.oraclecorp.com> Date: Mon, 09 Feb 2009 11:05:39 -0500 From: Chris Mason <chris.mason@...cle.com> To: Kyle McMartin <kyle@...radead.org> Cc: Chuck Ebbert <cebbert@...hat.com>, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu> Subject: Re: Build failure with latest -git: btrfs on ppc64 On Mon, 2009-02-09 at 10:57 -0500, Kyle McMartin wrote: > On Mon, Feb 09, 2009 at 09:57:26AM -0500, Chris Mason wrote: > > > > Ok, I thought this would be defined to something simple for the > > non-ticket users, should I just not be using this call? > > > > I think the use is fine, since it's really a judgement call based on > whether there's waiters for the ticket. I need to take a closer look > at where this is used to say... > The Btrfs use goes something like this: I'm about to wait for the disk. If there are other procs waiting for the locks I'm holding, I'll drop my locks and do a somewhat expensive btree search over again later so the waiters can make progress. If nobody is waiting, I'll do my read with my locks held so that I don't have to search again. > It's inevitable for you to hit things like this though, as far as I know > you're the first user of this lock interface. :) ;) -chris -- 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