From: Britt Park <britt@drscience.sciencething.org>
To: linux-kernel@vger.kernel.org
Subject: The demise of notify_change.
Date: Fri, 07 Dec 2001 21:19:35 -0800 [thread overview]
Message-ID: <3C11A2E7.5070306@sciencething.org> (raw)
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.
next reply other threads:[~2001-12-08 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 5:19 Britt Park [this message]
2001-12-10 2:41 ` The demise of notify_change Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C11A2E7.5070306@sciencething.org \
--to=britt@drscience.sciencething.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.