linux-kernel - Re: [PATCH v2] Add preadv and pwritev system calls.

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:	Fri, 12 Dec 2008 20:56:00 +0100
From:	Gerd Hoffmann <kraxel@...hat.com>
To:	Scott Lurndal <scott.lurndal@...afsystems.com>,
	Gerd Hoffmann <kraxel@...hat.com>,
	Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, Ulrich Drepper <drepper@...hat.com>
Subject: Re: [PATCH v2] Add preadv and pwritev system calls.

Russell King wrote:
>> should be similar to pread/pwrite, e.g:
>>
>>     int preadv(fd, iovec, iovec_size, offset)
> 
> Yes, and that's easy for glibc to achieve.

This hints the ABI problem exists at syscall level only.  Is that
correct?  So we can have

	preadv(fd, vec, vlen, off)

argument ordering at app <-> glibc level and

	preadv(fd, vec, off, vlen)

ordering at glibc <-> kernel (aka syscall) level and it works fine for
ARM + MIPS + PARISC?

thanks,
  Gerd


--
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/