Mime-Version: 1.0
Subject: =?UTF-8?B?UkU6IOetlOWkjTogW2YyZnMtZGV2XSBbUEFUQ0hdIGYyZnM6?=
 =?UTF-8?B?IHByZXZlbnQgbmV3bHkgY3JlYXRlZCBpbm9kZSBmcm9tIGJl?=
 =?UTF-8?B?aW5nIGRpcnRpZWQgaW5jb3JyZWN0bHk=?=
Reply-To: daeho.jeong@samsung.com
From: =?UTF-8?B?7KCV64yA7Zi4?= <daeho.jeong@samsung.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-f2fs-devel@lists.sourceforge.net" 
        <linux-f2fs-devel@lists.sourceforge.net>
In-Reply-To: <D642D0D599E2434C97EA15C58EE8D70E0832800E@DGGEMA501-MBX.china.huawei.com>
Message-ID: <20180112075903epcms1p4efb58a097d4ac19261aa2e78f2d49091@epcms1p4>
Date: Fri, 12 Jan 2018 07:59:03 +0000
Content-Transfer-Encoding: 8BIT
Content-Type: text/plain; charset="utf-8"
CMS-TYPE: 101P
DLP-Filter: Pass
References: <D642D0D599E2434C97EA15C58EE8D70E0832800E@DGGEMA501-MBX.china.huawei.com>
        <1515711960-10781-1-git-send-email-daeho.jeong@samsung.com>
        <CGME20180111230540epcas1p4c839d6dae432f5c1b388b43c17e0f649@epcms1p4>
Sender: linux-kernel-owner@vger.kernel.org

Hi Zhikang,

We dropped vfs caches periodically to reproduce the kernel panic using drop cache command.
I mean you have to trigger a checkpoint right after f2fs_mark_inode_dirty_sync() for a new inode.
We don't have any special test cases for that and we just triggered to drop caches periodically.
It was not easy to reproduce that, but it always occurrs within 24 hours.

Thanks,

 
--------- Original Message ---------
Sender : zhangzhikang <zhangzhikang1@huawei.com>
Date   : 2018-01-12 16:11 (GMT+9)
Title  : 答复: [f2fs-dev] [PATCH] f2fs: prevent newly created inode from being dirtied incorrectly
 
Hi Daeho:
 
We had tried to msleep(10000) after f2fs_mark_inode_dirty_sync() in creating a new file, and then write checkpoint in another thread.
But it didn't cause a kernel panic.
 
So can you tell me what test case did you use, and provide the call trace?
 
Thank you!
 
Best regards,
Zhikang Zhang