From: Chris Wright <chris@wirex.com>
To: Britt Park <britt@drscience.sciencething.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The demise of notify_change.
Date: Sun, 9 Dec 2001 18:41:47 -0800 [thread overview]
Message-ID: <20011209184147.A27109@figure1.int.wirex.com> (raw)
In-Reply-To: <3C11A2E7.5070306@sciencething.org>
In-Reply-To: <3C11A2E7.5070306@sciencething.org>; from britt@drscience.sciencething.org on Fri, Dec 07, 2001 at 09:19:35PM -0800
* 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
prev parent reply other threads:[~2001-12-10 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 5:19 The demise of notify_change Britt Park
2001-12-10 2:41 ` Chris Wright [this message]
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=20011209184147.A27109@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=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.