[lkml]   [2010]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] mlock: avoid dirtying pages and triggering writeback
On Thu, Nov 18, 2010 at 10:11:43AM +1100, Dave Chinner wrote:
> Hence I think that avoiding ->page_mkwrite callouts is likely to
> break some filesystems in subtle, undetected ways. IMO, regardless
> of what is done, it would be really good to start by writing a new
> regression test to exercise and encode the expected the mlock
> behaviour so we can detect regressions later on....

I think it would help if we could drink a bit of the test driven design
coolaid here. Michel, can you write some testcases where pages on a
shared mapping are mlocked, then dirtied and then munlocked, and then
written out using msync/fsync. Anything that fails this test on
btrfs/ext4/gfs/xfs/etc obviously doesn't work.

 \ /
  Last update: 2010-11-18 14:39    [W:0.082 / U:88.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site