Re: The demise of notify_change.

From: Chris Wright (
Date: Sun Dec 09 2001 - 21:41:47 EST

* Britt Park ( 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.

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

This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:16 EST