From owner-freebsd-stable@freebsd.org  Mon May  2 19:23:28 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
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 4498EB2A4B1
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon,  2 May 2016 19:23:28 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0B9C5167B
 for <freebsd-stable@freebsd.org>; Mon,  2 May 2016 19:23:28 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86_2 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1axJRK-0001lf-5y; Mon, 02 May 2016 21:23:30 +0200
Date: Mon, 2 May 2016 21:23:30 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Holger Kipp <Holger.Kipp@alogis.com>
Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject: Re: WARNING ioctl sign-extension  ioctl FFFFFFFF8004667e / CommVault
Message-ID: <20160502192330.GD2282@home.opsec.eu>
References: <810DA7C4-041E-44BA-B471-4207EB223A6A@alogis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <810DA7C4-041E-44BA-B471-4207EB223A6A@alogis.com>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2016 19:23:28 -0000

Hi!

> I get many CommVault-related warnings  (ioctl sign-extension
> ioctl) similar to those discussed for ages related to Python (June
> 2010 and before).

It seems this is a general problem, but mostly on the application
side. See for example:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147938

which shows that the application code uses the wrong type
for an ioctl argument.

> This only happens on amd64, not on the previously used i386 system,
> so might be 32/64bit related.

It looks like it's an application error. So maybe upstream (CommVault)
can comment on this ?

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !