lkml.org 
[lkml]   [1999]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC] What should we do with FAT inode numbers?
    Date
    From
    Alexander Viro <viro@math.psu.edu> wrote:
    > Problem: inode numbers on FAT-derived systems are completely
    > fscked up. Period. Amount of races in msdosfs code may exceed one in
    > MSDOS kernel (after all, the later is single-tasking). I hoped that we
    > might postpone fixing that stuff till 2.3, but...
    > FAT-derived filesystems use directory entry location as inode
    > number. ...

    I have understood that the *FAT format uses some chain of
    cluster indices, and unless the file *physically* moves,
    the head of the chain stays put, never mind possible renames
    et.al. even unlink won't change that value (thus fstat() will
    be stable for unlinked files too!)

    /Matti Aarnio <matti.aarnio@sonera.fi>

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

    \
     
     \ /
      Last update: 2005-03-22 13:49    [W:3.894 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site