Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ramsdell@mitre.org (John D. Ramsdell)
To: Alexander Viro <aviro@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: [PATCH] Reporting file descriptors created by pipe and socketpair
Date: 12 Sep 2006 15:22:02 -0400	[thread overview]
Message-ID: <ogtpse0yjol.fsf@divan.mitre.org> (raw)
In-Reply-To: <20060912162104.GK4144@devserv.devel.redhat.com>

Alexander Viro <aviro@redhat.com> writes:

> a) __NR_socketpair is not universally present
> b) neither __NR_socketpair nor __NR_pipe are guaranteed to be the

We have a fix for these issues which is in preparation, and will
submit the next version of the patch using the -urp option with diff.
Thank you for pointing out this problem.

John

      parent reply	other threads:[~2006-09-12 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 16:07 [PATCH] Reporting file descriptors created by pipe and socketpair John D. Ramsdell
2006-09-12 16:21 ` Alexander Viro
2006-09-12 17:41   ` Steve Grubb
2006-09-12 18:25   ` John D. Ramsdell
2006-09-12 19:12     ` Alexander Viro
2006-09-12 21:05       ` John D. Ramsdell
2006-09-12 19:22   ` John D. Ramsdell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ogtpse0yjol.fsf@divan.mitre.org \
    --to=ramsdell@mitre.org \
    --cc=aviro@redhat.com \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox