From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-15500-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 17611 invoked by alias); 19 Mar 2010 10:28:04 -0000
Received: (qmail 17560 invoked by uid 48); 19 Mar 2010 10:27:52 -0000
Date: Fri, 19 Mar 2010 10:28:00 -0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20100319102752.11402.mjw@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug tapsets/11402] New: pipe2 syscall not supported
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2010-q1/txt/msg00711.txt.bz2

The pipe2() was added to Linux in version 2.6.27. It is a variant of the normal
pipe syscall, but takes an extra flags argument which can be the ORed value of
O_NONBLOCK and O_CLOEXEC. The original pipe syscall is now defined as like the
pipe2 syscall, but with the flags variable set to zero.

Should we support this (in syscall2.stp) as an extra syscall, or should we
retrofit the syscall.pipe probe alias to also match sys_pipe2?

-- 
           Summary: pipe2 syscall not supported
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11402

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.