From: Toshi Kani <toshi.kani@hpe.com>
To: Eric Shang <EricShang@zhaoxin.com>,
Matthew Wilcox <willy@linux.intel.com>
Cc: "jack@suse.cz" <jack@suse.cz>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: ext4 error
Date: Wed, 13 Apr 2016 08:10:27 -0600 [thread overview]
Message-ID: <1460556627.24985.28.camel@hpe.com> (raw)
In-Reply-To: <0255994B402DE243B1DFC1057A00655201AC6F@ZXSHMBX02.zhaoxin.com>
On Wed, 2016-04-13 at 13:44 +0000, Eric Shang wrote:
> HI All:
> I meet an ext4 error, following is the error log. After panic, I check the
> emmc by the tool debufs, the inode 69878 i_nlink is not zero. And this inode
> don't belong to parent dir 6987, it belong to other file(this inode belong to
> two files when check by debugfs ncheck), I guess than this inode has beed
> deleted in memory and already used by other file. But the parent dentry
> buff_head not flush to emmc. But when lookup this dentry can't find it' in
> dentry cache, and then lookup_real, read the dentry from emmc, get the file
> inode which already be deleted.
> Can any give me some help how to check this issue. My kernel version is 3.18
> form Android . I thinks something wrong with dentry cache flush and dirty
> buff_head flush to emmc. Thanks all!
Are you somehow using DAX and my dax_get_unmapped_area patches in your Android
3.18 kernel? I doubt this is the case, but I thought I should check since you
reported it to me and Matthew with the same cc list.
If you are simply using a distributed Android kernel, you should report it to
Android email list or bug tracker.
-Toshi
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-13 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 13:44 ext4 error Eric Shang
2016-04-13 14:10 ` Toshi Kani [this message]
2016-04-14 2:02 ` 答复: " Eric Shang
2016-04-14 3:22 ` Theodore Ts'o
2016-04-14 6:33 ` 答复: " Eric Shang
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=1460556627.24985.28.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=EricShang@zhaoxin.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=xfs@oss.sgi.com \
/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