[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120530174858.GN15587@linux.vnet.ibm.com>
Date: Wed, 30 May 2012 23:18:58 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Anton Arapov <anton@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] uprobes: simplify the usage of uprobe->pending_list
* Oleg Nesterov <oleg@...hat.com> [2012-05-30 18:58:46]:
> uprobe->pending_list is only used to create the temporary list,
> it has no meaning after we drop uprobes_mmap_hash(inode).
>
> No need to initialize this node or remove it from tmp_list, and
> we can use list_for_each_entry().
I actually dont see the patch that removed the uprobe->pending_list.
I dont see it as part of the 7 that you sent yesterday. Nor does is it
part of the series that you sent today.
the uprobe_mmap_hash was required because we can do only one insert or
remove operation at a time.
How are we going to synchronize uprobe_mmap() for two different vmas
that belong two different mms but map the same inode?
May be I am missing a patch somewhere.
--
thanks and regards
Srikar
--
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