public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Eric Paris <eparis@redhat.com>,
	david@lang.hm, bunk@kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org, malware-list@lists.printk.net,
	hch@infradead.org, andi@firstfloor.org, viro@ZenIV.linux.org.uk,
	arjan@infradead.org
Subject: Re: [malware-list] [RFC] 0/11 fanotify: fscking all notifiction and file access system (intended for antivirus scanning and file indexers)
Date: Fri, 26 Sep 2008 14:48:47 -0700	[thread overview]
Message-ID: <20080926214847.GA9592@kroah.com> (raw)
In-Reply-To: <20080926223404.7c4894df@lxorguk.ukuu.org.uk>

On Fri, Sep 26, 2008 at 10:34:04PM +0100, Alan Cox wrote:
> > It all starts when 'something' registers a group.  Registering a group
> > is as simple as 'echo "open_grp 50 0x10" > /security/fanotify/register.
> 
> I thought the operation was usually called "mkdir" which also nicely
> deals with races and exclusion.

So does configfs.  Eric, why not use that instead, it sounds like it
will work here nicely.

thanks,

greg k-h

  reply	other threads:[~2008-09-26 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 21:07 [RFC] 0/11 fanotify: fscking all notifiction and file access system (intended for antivirus scanning and file indexers) Eric Paris
2008-09-26 21:34 ` Alan Cox
2008-09-26 21:48   ` Greg KH [this message]
2008-09-26 22:03   ` Eric Paris
2008-10-02 19:24   ` Eric Paris
2008-10-02 20:48     ` Alan Cox
2008-09-27  6:05 ` david
2008-09-27 11:20   ` Alan Cox
2008-10-06 15:09     ` Pavel Machek
2008-09-27 14:04   ` Eric Paris
     [not found]     ` <5CB739747AC639489F3E8210950C3E555C39EE@geousmail3.GEO.CORP.HCL.IN>
2008-10-07 17:36       ` [malware-list] [RFC] 0/11 fanotify: fscking all notifiction andfile access system (intended for antivirus scanning and fileindexers) Eric Paris

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=20080926214847.GA9592@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=bunk@kernel.org \
    --cc=david@lang.hm \
    --cc=eparis@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malware-list@lists.printk.net \
    --cc=peterz@infradead.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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