linux-kernel - RE: 答复: [f2fs-dev] [PATCH] f2fs: prevent newly created inode from being dirtied incorrectly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20180112075903epcms1p4efb58a097d4ac19261aa2e78f2d49091@epcms1p4>
Date:   Fri, 12 Jan 2018 07:59:03 +0000
From:   정대호 <daeho.jeong@...sung.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-f2fs-devel@...ts.sourceforge.net" 
        <linux-f2fs-devel@...ts.sourceforge.net>
Subject: RE: 答复: [f2fs-dev] [PATCH] f2fs: prevent newly created inode from being dirtied incorrectly

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@...wei.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