From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Odd NFS related SIGBUS (& possible fix) Date: Wed, 29 Sep 2010 17:44:42 +1000 Message-ID: <1285746282.14081.89.camel@pasglop> References: <1285734825.14081.87.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Trond Myklebust , "linux-kernel@vger.kernel.org" , Al Viro , linux-fsdevel@vger.kernel.org To: Nick Piggin Return-path: In-Reply-To: <1285734825.14081.87.camel@pasglop> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 2010-09-29 at 14:33 +1000, Benjamin Herrenschmidt wrote: > Now regarding the other bug, unless Trond has an idea already, I think I'll start > a separate email thread once I've collected more data. I -think- it invalidates it > because it sees a the server mtime that is more recent than the inode, but the > server shouldn't be touching at files, so I suspect we get confused somewhere in > the kernel and I don't know why yet (the code path inside NFS aren't obvious to > me at this stage). Ok, so that doesn't happen with current upstream (we were on some 2.6.32.16 based kernel here). I'll figure that out from there. However, I still think there's a potential erroneous sigbus in the NFS page_mkwrite() code path unless I'm mistaken. Cheers, Ben.