lkml.org 
[lkml]   [2008]   [Dec]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [take2] Inotify: nested attributes support.
On Thu, Dec 04, 2008 at 09:43:10AM +0100, Pavel Machek (pavel@suse.cz) wrote:
> Actually, does the kernel even know who initiated the i/o?
>
> Take two threads, both mapping /etc/something , both of them writing
> through the mmap. Kernel sees dirty pages so it writes them back, but
> which thread is repsonsible for the write?

It depends. If write will be done with write() syscall, caller will be
stored. Otherwise inotify does not hook into page fault code afaics.

> > > 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).
>
> What happens on mmap()?

mmap() syscall is not processed by inotify.

--
Evgeniy Polyakov


\
 
 \ /
  Last update: 2008-12-04 10:11    [W:0.075 / U:0.632 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site