From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@kernel.dk>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: Odd NFS related SIGBUS (& possible fix)
Date: Wed, 29 Sep 2010 17:44:42 +1000 [thread overview]
Message-ID: <1285746282.14081.89.camel@pasglop> (raw)
In-Reply-To: <1285734825.14081.87.camel@pasglop>
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.
next prev parent reply other threads:[~2010-09-29 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 4:33 Odd NFS related SIGBUS (& possible fix) Benjamin Herrenschmidt
2010-09-29 7:44 ` Benjamin Herrenschmidt [this message]
2010-10-01 5:57 ` Benjamin Herrenschmidt
2010-10-01 5:57 ` Benjamin Herrenschmidt
2010-10-01 6:01 ` Benjamin Herrenschmidt
2010-10-01 6:01 ` Benjamin Herrenschmidt
2010-10-01 17:18 ` J. Bruce Fields
2010-10-01 18:12 ` Trond Myklebust
2010-10-01 18:35 ` Trond Myklebust
2010-10-01 20:57 ` Benjamin Herrenschmidt
2010-10-18 23:43 ` Benjamin Herrenschmidt
2010-10-01 20:53 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1285746282.14081.89.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.