Re: The demise of notify_change.

[Chris Wright]

* Britt Park ([e-mail]) wrote:
> 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?

read fs/attr.c::notify_change(), i believe the inode_operations->setattr()
is what you are looking for.

cheers,
-chris