[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1248898329.2597.57.camel@localhost>
Date: Wed, 29 Jul 2009 16:12:09 -0400
From: Eric Paris <eparis@...hat.com>
To: Andreas Dilger <adilger@....com>
Cc: Jamie Lokier <jamie@...reable.org>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, malware-list@...sg.printk.net,
Valdis.Kletnieks@...edu, greg@...ah.com, jcm@...hat.com,
douglas.leeder@...hos.com, tytso@....edu, arjan@...radead.org,
david@...g.hm, jengelh@...ozas.de, aviro@...hat.com,
mrkafk@...il.com, alexl@...hat.com, jack@...e.cz,
tvrtko.ursulin@...hos.com, a.p.zijlstra@...llo.nl,
hch@...radead.org, alan@...rguk.ukuu.org.uk, mmorley@....in,
pavel@...e.cz
Subject: Re: fanotify - overall design before I start sending patches
On Mon, 2009-07-27 at 12:33 -0600, Andreas Dilger wrote:
> On Jul 25, 2009 01:29 +0100, Jamie Lokier wrote:
> It might also make sense to verify that the process doing the open has
> at least permission to open the file in question (i.e. root) so that
> some unauthorized process cannot just get file handles to arbitrary files.
All current permissions between the listener process and the object are
done. It's quite possible to get fanotify events where the fd = -EPERM.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists