From: John McCutchan <ttb@tentacle.dhs.org>
To: Robert Love <rml@novell.com>
Cc: marijn ros <marijn@mad.scientist.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] fsnotify: hook on removexattr, too
Date: Fri, 05 Aug 2005 16:05:16 -0400 [thread overview]
Message-ID: <1123272316.28473.0.camel@vertex> (raw)
In-Reply-To: <1123271715.30486.82.camel@betsy>
On Fri, 2005-08-05 at 15:55 -0400, Robert Love wrote:
> On Fri, 2005-08-05 at 19:07 +0100, marijn ros wrote:
>
> > I got wondering, why does fs_notify_xattr get called from setxattr in fs/xattr.c, but
> > not from removexattr that is below it in the same file? Both seem to make changes to
> > xattrs and both are exported as system calls.
>
> We should.
>
Yes we should.
Signed-off-by: John McCtuchan <ttb@tentacle.dhs.org>
--
John McCutchan <ttb@tentacle.dhs.org>
prev parent reply other threads:[~2005-08-05 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 18:07 fsnotify on removexattr marijn ros
2005-08-05 19:55 ` [patch] fsnotify: hook on removexattr, too Robert Love
2005-08-05 20:05 ` John McCutchan [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=1123272316.28473.0.camel@vertex \
--to=ttb@tentacle.dhs.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn@mad.scientist.com \
--cc=rml@novell.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox