Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752980AbcDNCDH (ORCPT ); Wed, 13 Apr 2016 22:03:07 -0400 Received: from [180.169.121.82] ([180.169.121.82]:13842 "EHLO ZXSHCAS01.zhaoxin.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752895AbcDNCDF (ORCPT ); Wed, 13 Apr 2016 22:03:05 -0400 From: Eric Shang To: Toshi Kani , Matthew Wilcox CC: "akpm@linux-foundation.org" , "dan.j.williams@intel.com" , "viro@zeniv.linux.org.uk" , "ross.zwisler@linux.intel.com" , "kirill.shutemov@linux.intel.com" , "david@fromorbit.com" , "jack@suse.cz" , "tytso@mit.edu" , "adilger.kernel@dilger.ca" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "linux-ext4@vger.kernel.org" , "xfs@oss.sgi.com" , "linux-kernel@vger.kernel.org" Subject: =?utf-8?B?562U5aSNOiBleHQ0IGVycm9y?= Thread-Topic: ext4 error Thread-Index: AQHRlY9dNaCFWilxVEKHk4Jt5qZ+V5+ItrDg Date: Thu, 14 Apr 2016 02:02:18 +0000 Message-ID: <0255994B402DE243B1DFC1057A00655201AE84@ZXSHMBX02.zhaoxin.com> References: <0255994B402DE243B1DFC1057A00655201AC6F@ZXSHMBX02.zhaoxin.com> <1460556627.24985.28.camel@hpe.com> In-Reply-To: <1460556627.24985.28.camel@hpe.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.30.24.50] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u3E23B61023070 Content-Length: 1976 Lines: 34 Hi Toshi: Thanks! I think this not relate to DAX and dax_get_unmapped_area, I am a junior kernel maintainer for our company. This issue bother me long time, looks like kernel ext4 issue or our emmc driver issue, I will dig it out, Thanks! Best Regards EricShang -----邮件原件----- 发件人: Toshi Kani [mailto:toshi.kani@hpe.com] 发送时间: 2016年4月13日 22:10 收件人: Eric Shang; Matthew Wilcox 抄送: akpm@linux-foundation.org; dan.j.williams@intel.com; viro@zeniv.linux.org.uk; ross.zwisler@linux.intel.com; kirill.shutemov@linux.intel.com; david@fromorbit.com; jack@suse.cz; tytso@mit.edu; adilger.kernel@dilger.ca; linux-nvdimm@lists.01.org; linux-fsdevel@vger.kernel.org; linux-ext4@vger.kernel.org; xfs@oss.sgi.com; linux-kernel@vger.kernel.org 主题: Re: ext4 error 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