* The demise of notify_change.
@ 2001-12-08 5:19 Britt Park
2001-12-10 2:41 ` Chris Wright
0 siblings, 1 reply; 2+ messages in thread
From: Britt Park @ 2001-12-08 5:19 UTC (permalink / raw)
To: linux-kernel
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.),
Britt
P.S. I promise to send REG amendments to his VFS doc when I get done.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: The demise of notify_change.
2001-12-08 5:19 The demise of notify_change Britt Park
@ 2001-12-10 2:41 ` Chris Wright
0 siblings, 0 replies; 2+ messages in thread
From: Chris Wright @ 2001-12-10 2:41 UTC (permalink / raw)
To: Britt Park; +Cc: linux-kernel
* 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-12-10 2:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-08 5:19 The demise of notify_change Britt Park
2001-12-10 2:41 ` Chris Wright
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox