From: Jeff Moyer <jmoyer@redhat.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Nick Piggin <npiggin@novell.com>, Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NULL inode->i_mapping in generic_sync_sb_inodes
Date: Wed, 07 Oct 2009 09:15:47 -0400 [thread overview]
Message-ID: <x497hv7tke4.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20091007124327.GT30316@wotan.suse.de> (Nick Piggin's message of "Wed, 7 Oct 2009 14:43:27 +0200")
Nick Piggin <npiggin@suse.de> writes:
>> hch mentioned that it would be good to instrument to what file system
>> the inode belonged. Anything else you'd like to look at?
>
> Not too sure. I guess i_state. Maybe you could take s_umount lock
> and see if it is still mounted?
>
> Actually most useful will be to find all places where i_mapping is
> set to NULL, and record in the inode some callchain for the last
> site which set i_mapping to NULL. Dump this stack when you hit the
> bug.
Well, I can't find a single place where i_mapping is set to NULL. ;-)
I'll see what I can dig up.
Cheers,
Jeff
next prev parent reply other threads:[~2009-10-07 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ACC9E8A0200008A000439B0@novprvlin0050.provo.novell.com>
2009-10-07 12:05 ` NULL inode->i_mapping in generic_sync_sb_inodes Jeff Moyer
2009-10-07 12:43 ` Nick Piggin
2009-10-07 13:15 ` Jeff Moyer [this message]
2009-10-06 13:48 Jeff Moyer
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=x497hv7tke4.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@novell.com \
--cc=npiggin@suse.de \
/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).