From owner-freebsd-stable@freebsd.org Mon May 2 15:26:40 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC140B2A922 for ; Mon, 2 May 2016 15:26:40 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (firewall.alogis.com [212.184.102.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4927A11A3 for ; Mon, 2 May 2016 15:26:39 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from msx3.exchange.alogis.com (msxcn2.exchange.alogis.com [10.1.1.22]) by alogis.com (8.13.4/8.13.1) with ESMTP id u42FM3UJ004990 for ; Mon, 2 May 2016 17:22:03 +0200 (CEST) (envelope-from Holger.Kipp@alogis.com) Received: from MSX3.exchange.alogis.com ([10.1.1.26]) by msxcn2.exchange.alogis.com ([fe80::11b6:f5c4:b8ee:4a89%15]) with mapi id 14.03.0279.002; Mon, 2 May 2016 17:22:03 +0200 From: Holger Kipp To: "freebsd-stable@freebsd.org" Subject: WARNING ioctl sign-extension ioctl FFFFFFFF8004667e / CommVault Thread-Topic: WARNING ioctl sign-extension ioctl FFFFFFFF8004667e / CommVault Thread-Index: AdGkhmCXwaV2ruuHS2aZJtLg4EcoXg== Date: Mon, 2 May 2016 15:22:02 +0000 Message-ID: <810DA7C4-041E-44BA-B471-4207EB223A6A@alogis.com> Accept-Language: de-DE, en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-ID: <50C468DAFB068345BD03F13DB8CE1A73@exchange.alogis.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 15:26:40 -0000 Dear all, on a quite fresh vanilla (read: GENERIC) FreeBSD 10.2-RELEASE-p14 (amd64)=20 I get many CommVault-related warnings (ioctl sign-extension ioctl) similar= to those discussed for ages related to Python (June 2010 and before). This only happens on amd64, not on the previously used i386 system, so migh= t be 32/64bit related. It seems this is because IOC_IN is defined as 0x80000000 (integer) in /usr/= include/sys/ioccom.h so could it be an internal handling problem instead of= calling ioctl with a wrong int/unsigned int from external program? I only see these warnings in /var/log/messages with ffffffff8004667e but th= at might be unrelated. I'like to get rid of these warnings (preferably with the generic kernel). Any ideas? - I'm not a C programmer so can't really dig into this :-( Many thanks and best regards, Holger =