lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b82a89170812200513q1a27b62ap590fb6fbad930a@mail.gmail.com>
Date:	Sat, 20 Dec 2008 18:43:01 +0530
From:	"Niraj kumar" <niraj17@...il.com>
To:	"Evgeniy Polyakov" <zbr@...emap.net>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [Question] inotify : process based filtering of events

>>
>> Is it possible to achieve this process based filtering of events
>> using inotify infrastructure?
>
> You can try using inotify nested attributes patch [1] and filter events
> in userspace based on reported pid/tid.

I saw your patch and the related discussion...
But I am thinking that filtering in userspace based on pid/tid
could be too much overhead when the data that I am interested
in might be just a small fraction of the whole thing...

I was hoping to add a flag (similar to IN_ATTRS that you have added)
which, when used, will only collect events for the calling
process and it's children...

-Niraj
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ