Messages in this thread | | | Date | Sun, 9 Dec 2001 18:41:47 -0800 | From | Chris Wright <> | Subject | Re: The demise of notify_change. |
| |
* Britt Park (britt@drscience.sciencething.org) 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |