From: "Will Simoneau" <simoneau@ele.uri.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: lockdep splat: nfsroot on 2.6.39-rc2
Date: Mon, 11 Apr 2011 03:23:07 -0400 [thread overview]
Message-ID: <20110411072306.GA17806@ele.uri.edu> (raw)
In-Reply-To: <20110411040209.GA21395@dastard>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On 14:02 Mon 11 Apr , Dave Chinner wrote:
> On Sat, Apr 09, 2011 at 10:55:02PM -0400, Will Simoneau wrote:
> > This seems to happen consistently when running "apt-get update". Ideas?
> > Known bug?
>
> The bug is in nfs_commit_inode(), where it calls nfs_scan_commit()
> with the inode->i_lock held and that calls __mark_inode_dirty()
> which takes the inode->i_lock....
>
> The patch below should fix this problem.
I can confirm that your patch fixes the issue. Thanks for the fix!
Tested-by: Will Simoneau <simoneau@ele.uri.edu>
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-04-11 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110410025502.GA15112@ele.uri.edu>
2011-04-11 4:02 ` lockdep splat: nfsroot on 2.6.39-rc2 Dave Chinner
2011-04-11 7:23 ` Will Simoneau [this message]
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=20110411072306.GA17806@ele.uri.edu \
--to=simoneau@ele.uri.edu \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).