linux-kernel - Re: vmsplice complains bad address

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] [day] [month] [year] [list]

Message-ID: <20060825171430.GG24258@kernel.dk>
Date:	Fri, 25 Aug 2006 19:14:30 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	Yi Yang <yang.y.yi@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: vmsplice complains bad address

On Fri, Aug 25 2006, Yi Yang wrote:
> Hi, Jens
> 
> When I tested vmsplice syscall, it always complains bad address, I don't
> understand why, does vmsplice have a special reqiurement for address
> alignment?
> 
> The following file is a test program which is extracted from your patch
> and modified in order to adapt to the latest interface. its output is:
> 
> getpagesize = 4096
> page size: 4096 bytes
> vmsplice: Bad address
> here: len = 4096, written = -1

First of all, please send code that is actually readable (eg indent it
and if your mailer writes lines (which it does), then attach it instead
of inlining).

What arch are you testing on? If x86-64, you have an error:

> //#include "splice.h"
> #if defined(__i386__)
> #define __NR_splice 313
> #define __NR_tee 315
> #define __NR_vmsplice 316
> #elif defined(__x86_64__)
> #define __NR_splice 275
> #define __NR_tee 276
> #define __NR_vmsplice 277

vmsplice is 278

-- 
Jens Axboe

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