freebsd stable - May 2016 - WARNING ioctl sign-extension ioctl FFFFFFFF8004667e / CommVault

Dear all,

on a quite fresh vanilla (read: GENERIC)

FreeBSD 10.2-RELEASE-p14 (amd64) 

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 might 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 that
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

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 at opsec.eu            +49 171 3101372                         4 years to go
!