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]

Date:	Mon, 6 Jul 2009 14:23:53 +0800
From:	Changli Gao <xiaosuo@...il.com>
To:	Albert ARIBAUD <albert.aribaud@...e.fr>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Amerigo Wang <xiyou.wangcong@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: PROPOSAL: extend pipe() to support NULL argument.

On Mon, Jul 6, 2009 at 2:15 PM, Albert ARIBAUD<albert.aribaud@...e.fr> wrote:
>>
>>
>> pipe doesn't support llseek.
>
> I wasn't thinking of actively seeking a file position, but simply that reads
> and writes were independent (and both variable) in size, thus even without
> (l)seeking, each endpoint has an independent read (resp. write) position to
> track what's been read from (resp.written into) it at any time, and such a
> position is, IIUC, single for a given fd, making a fd (a struct file)
> insufficient for representing a pipe.
>
> Amicalement,
> --
> Albert.
>
pipe doesn't refer to pos when reading or writing. Please refer to
pipe_read() and pipe_write() for more detail.


-- 
Regards，
Changli Gao(xiaosuo@...il.com)
--
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/