linux-kernel - Re: NFSv4: Give the lock stateid its own sequence queue

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47868D4B.6030608@garzik.org>
Date:	Thu, 10 Jan 2008 16:25:31 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Trond Myklebust <Trond.Myklebust@...app.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: NFSv4: Give the lock stateid its own sequence queue

Trond Myklebust wrote:
> Sharing the open sequence queue causes a deadlock when we try to take both
> a lock sequence id and and open sequence id.
> 
> This fixes the regression reported by Dimitri Puzin and Jeff Garzik:
> See http://bugzilla.kernel.org/show_bug.cgi?id=9712
> 
> Signed-off-by: Trond Myklebust <Trond.Myklebust@...app.com>

Tested-by: Jeff Garzik <jgarzik@...hat.com>


--
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/