linux-kernel - Re: PROPOSAL: extend pipe() to support NULL argument.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090702091309.GB6372@cr0.nay.redhat.com>
Date:	Thu, 2 Jul 2009 17:13:09 +0800
From:	Amerigo Wang <xiyou.wangcong@...il.com>
To:	Changli Gao <xiaosuo@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: PROPOSAL: extend pipe() to support NULL argument.

On Thu, Jul 02, 2009 at 03:36:41PM +0800, Changli Gao wrote:
>Linux also uses pipes as references of kernel buffers. In that case,
>only one RW file descriptor will be enough, instead of inventing a new
>system call, I think extending the existing pipe() is a better idea.
>If pipe is passed with a NULL pointer, one RW file descriptor is
>returned. I have checkd the other architectures except of x86, it
>seems that not all of the platforms implement this system call with
>the prototype: int pipe(int fd[2]); and changing glibc is needed. Is
>it possible to extend pipe() in this way?
>

Why? Why do you need this feature?
--
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/