linux-kernel - Writing tests for write back

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: <532480950801071047xf7fa0b7te3967484a34190a7@mail.gmail.com>
Date:	Mon, 7 Jan 2008 10:47:27 -0800
From:	"Michael Rubin" <mrubin@...gle.com>
To:	linux-kernel@...r.kernel.org,
	"WU Fengguang" <wfg@...l.ustc.edu.cn>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Writing tests for write back

I am writing tests for the write back section of the kernel. This is
the stuff found in fs/fs-writeback.c.

Currently I have tests to fsync millions of inodes concurrently, tests
involving mounting and unmounting file systems, and other tests to
tickle some starvation of big file situations. Has anyone else been
bitten by writeback not performing correctly either in the past or
now? If so please send me the situation so I can incorporate it into
my tests and also make sure my new attempt at an implementation does
not cause damage.

These tests will end up in autotest on test.kernel.org so they will
become something the whole community can use.

mrubin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/