Date: Sun, 13 Dec 2009 11:07:53 -0800 (PST)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
       Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Andrew Morton <akpm@linux-foundation.org>, Greg KH <gregkh@suse.de>,
       Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] TTY patches for 2.6.33-git
In-Reply-To: <1260729195.2612.7.camel@localhost>
Message-ID: <alpine.LFD.2.00.0912131052080.13952@localhost.localdomain>
References: <20091212101032.GB25286@elte.hu>  <20091212023603.93768833.akpm@linux-foundation.org>  <alpine.LFD.2.00.0912120915390.3526@localhost.localdomain>  <alpine.LFD.2.00.0912120920190.3526@localhost.localdomain>  <20091212214235.31429790@lxorguk.ukuu.org.uk>
  <alpine.LFD.2.00.0912121418490.3526@localhost.localdomain>  <alpine.LFD.2.00.0912122331200.3089@localhost.localdomain>  <alpine.LFD.2.00.0912121513190.3535@localhost.localdomain>  <20091213065844.GA20244@elte.hu>  <alpine.LFD.2.00.0912130941050.5516@localhost.localdomain>
  <20091213181726.GA14558@elte.hu> <1260729195.2612.7.camel@localhost>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1186
Lines: 28


On Sun, 13 Dec 2009, Trond Myklebust wrote:
> 
> The main remaining problem area is that of file locking (i.e. anything
> that references inode->i_flock). I've started work on that, but a couple
> of higher interrupts have prevented me from pulling it all together in
> time for this merge window...

I'm pretty sure we've had at least two trees with the file locking code 
fixed, but NFS in a status of "unknown".

If I recall correctly, the file locking code itself is not that hard: 
we've done it without the kernel lock in the past (long long ago), and the 
lock usage doesn't nest (or at least it didn't at some point back then ;). 
In fact, I think we even do the actual lock data structure allocations 
outside of the kernel lock exactly because we at one time had a patch that 
used a spinlock for protection of the lists.

(Again, not only my memory, but the code itself may have bitrotted in the 
meantime, of course).

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/