[lkml]   [2001]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectThe demise of notify_change.
Somewhen between 2.2.x and 2.4.x notify_change disappeared from 
super_operations. What is the accepted practice now for updating an
inode's persistent state? Should one use write_inode for the same
purpose or should one rely on file_operations::setattr (excuse the
c++ism)? Or is there something entirely different that one should do?

With apologies for being behind the times (I'm trying to update a
filesystem I wrote for 2.0.x, which fact dates me accurately.),


P.S. I promise to send REG amendments to his VFS doc when I get done.

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: 2005-03-22 13:13    [W:0.038 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site