linux-kernel - Re: [take2] Inotify: nested attributes support.

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: <20081126082936.GB17525@ioremap.net>
Date:	Wed, 26 Nov 2008 11:29:36 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	john@...nmccutchan.com, arnd@...db.de, mtk.manpages@...il.com,
	hch@....de, rlove@...ve.org, linux-api@...r.kernel.org,
	linux-kernel@...r.kernel.org, pavel@...e.cz,
	davidn@...idnewall.com, Eric Paris <eparis@...hat.com>
Subject: Re: [take2] Inotify: nested attributes support.

On Wed, Nov 26, 2008 at 12:15:38AM -0800, Andrew Morton (akpm@...ux-foundation.org) wrote:
> OK, so we have a super-duper framework which will allow us to add pids
> (and other things) to inotify messages.

Yup :)

> This still doesn't provide a reason for anyone to be interested in the
> code!  Why do we want pids in inotify messages?

I actually cared only about myself :)
I started the thread and implementation, because my application has to
differentiate IO made by itself and any IO made by system (another
users, crons, whatever else), inotify did not give me that info, so I
extended it. As of others: PID/TID may be used by watching applications
to reduce own load to not process own IO, things like beagle may show
who actually made changes into the file.

> And how does this work give that pids are (no longer) system-wide unique?

It gets pids from the caller's task_struct (via current), so its data is
as unique as process calling getpid() or syscall(__NR_gettid).

-- 
	Evgeniy Polyakov
--
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/