[lkml]   [2006]   [Dec]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRecent mm changes leading to filesystem corruption?
    Debian recently applied a number of mm changes that went into 2.6.19
    to their 2.6.18 kernel for LSB 3.1 compliance (msync() had problems
    before). Since then, some filesystem corruption has been observed
    which can be traced back to these mm changes. Is anyone aware of
    problems with these patches?

    The patches that were applied are:

    - mm: tracking shared dirty pages
    - mm: balance dirty pages
    - mm: optimize the new mprotect() code a bit
    - mm: small cleanup of install_page()
    - mm: fixup do_wp_page()
    - mm: msync() cleanup

    With these applied to 2.6.18, the Debian installer on a slow ARM
    system fails because a program segfaults due to filesystem corruption: This problem also occurs if you only
    apply the "mm: tracking shared dirty pages" patch to 2.6.18 from the
    series of 5 patches listed above.

    Another problem has been reported related to libtorrent: according to someone also saw this with non-Debian
    2.6.19 but obviously it's hard to say whether the bugs are really
    related.;msg=24 shows
    some dmesg messages but again it's not 100% clear it's the same bug.

    Has anyone else seen problems or is aware of a fix to the patches
    listed above that I'm unaware of? It's possible the problem only
    shows up on slow systems. (The corruption is reproducible on a slow
    NSLU2 ARM system with 32 MB ram, but it doesn't happen on a faster ARM
    box with more RAM.)
    Martin Michlmayr
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-12-16 17:19    [W:0.020 / U:13.236 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site