From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3559 invoked by alias); 4 Sep 2009 18:08:16 -0000 Received: (qmail 3514 invoked by uid 48); 4 Sep 2009 18:08:04 -0000 Date: Fri, 04 Sep 2009 18:08:00 -0000 Message-ID: <20090904180804.3513.qmail@sourceware.org> From: "jkenisto at us dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090903122458.10595.mjw@redhat.com> References: <20090903122458.10595.mjw@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug uprobes/10595] uprobe probes causes selinux failures X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q3/txt/msg00576.txt.bz2 ------- Additional Comments From jkenisto at us dot ibm dot com 2009-09-04 18:08 ------- (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #5) > > > Created an attachment (id=4170) --> (http://sourceware.org/bugzilla/attachment.cgi?id=4170&action=view) > > > ssol-vma-selinux patch using shmem_file_setup > > > > At this point > > if (addr & ~PAGE_MASK) { > > addr will be undefined if shmem_file_setup() returned NULL. > > addr would be 0 if !file, since earlier in the function we have: > > if ((addr = find_old_ssol_vma()) != 0) > return addr; You're right, it'd be 0. But with above test, addr==0 would look like success. > > > Yes, runtime/uprobes/uprobes.c and ubp_xol.c (?) in the ubp-based uprobes bits. > > Thanks, mjw. Srikar, are you going to take it from here? > > I found fche's utrace-ext.git repo, is that where those are now? I can certainly > build that and supply a patch for it. Which branch should it be against? > utrace-uprobes or utrace-gdbstub-uprobes? Does that uprobes kernel module > version work against systemtap git? Sorry, I haven't been keeping up with that code base except via code reviews. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10595 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.