From owner-freebsd-emulation Sun Feb 14 02:31:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10881 for freebsd-emulation-outgoing; Sun, 14 Feb 1999 02:31:06 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from storage.delta.odessa.ua (korona.TM.Odessa.UA [195.66.192.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10867 for ; Sun, 14 Feb 1999 02:30:55 -0800 (PST) (envelope-from vns@delta.odessa.ua) Received: (from vns@localhost) by storage.delta.odessa.ua (8.9.2/8.8.8) id MAA00613 for freebsd-emulation@freebsd.org; Sun, 14 Feb 1999 12:30:23 +0200 (EET) (envelope-from vns) Date: Sun, 14 Feb 1999 12:30:23 +0200 (EET) From: "Vladimir N.Silyaev" Message-Id: <199902141030.MAA00613@storage.delta.odessa.ua> To: freebsd-emulation@FreeBSD.ORG Subject: Linux async I/O Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Anybody can explain status of native Linux async I/O? Some pieces code frome linux 2.0.33 kernel. -------------- cut here ---------------------- case FIOSETOWN: case SIOCSPGRP: err=verify_area(VERIFY_READ,(int *)arg,sizeof(long)); if(err) return err; pid = get_user((int *) arg); /* see inet_fcntl */ if (current->pid != pid && current->pgrp != -pid && !suser()) return -EPERM; sk->proc = pid; return(0); -------------- cut here ---------------------- Linux kernel don't make difference on FIOSETOWN and SIOCSPGRP! But FreeBSD kernel code and Linux emulation subsystem, work sligthly differently (I mean FreeBSD do it with accordance to POSIX standarts). There are in FIOSETOWN call positive value mean the process id, negative is the process group id and SIOCSPGRP vice versa positive is the process group id, and negative is the process id. Our comments? With best regards, V.Silyaev. P.S. It's a main reason why SYBASE SQL SERVER don't working on the current. It's call SIOCSPGRP with value from getpid, without creating process group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message