From owner-freebsd-questions@freebsd.org Fri Aug 4 20:09:50 2017 Return-Path: Delivered-To: freebsd-questions@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 378C4DC69EE for ; Fri, 4 Aug 2017 20:09:50 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: from trent.utfs.org (trent.utfs.org [94.185.90.103]) (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 F328575FAC for ; Fri, 4 Aug 2017 20:09:49 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: from localhost (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by trent.utfs.org (Postfix) with ESMTPS id 01ADD5F8F4; Fri, 4 Aug 2017 22:09:47 +0200 (CEST) Date: Fri, 4 Aug 2017 13:09:46 -0700 (PDT) From: Christian Kujau To: Per olof Ljungmark cc: freebsd-questions@freebsd.org Subject: Re: ioctl sign-extensio on amd64 (again) In-Reply-To: Message-ID: References: <444dc69b-c586-7e0b-61c8-77a2bc722516@intersonic.se> User-Agent: Alpine 2.21.1 (DEB 211 2017-05-04) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Aug 2017 20:09:50 -0000 On Fri, 4 Aug 2017, Christian Kujau wrote: > On Fri, 4 Aug 2017, Per olof Ljungmark wrote: > > In building a camera system with multimedia/motion, syslog is filled up with, > > kernel: WARNING pid 72755 (motion): ioctl sign-extension ioctl > > ffffffffc0585611 > > > > After som googling this appears to be a long standing problem with some python > > stuff and amd64. > > > > My question is, how can I get rid of the messages? Motion works as expected, I > > just do not want this filling up the logs. > > Short of disabling the printf in sys_ioctl() in sys/kern/sys_generic.c, > the Right Thing To Do™ would be to fix multimedia/motion not to issue > those erroneous ioctls. This was reported (and sometimes fixed) for other > applications too: > > * sysutils/duplicity-devel/ throws ioctl sign-extension ioctl ffffffff80087467 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=152770 > > * mt(8): ioctl sign-extension warnings from some mt commands on 64-bit > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147938 > > * Fix fcntl module to accept 'unsigned long' type commands for ioctl(2). > https://bugs.python.org/issue25026 > > Maybe the respective commits could shed some light on how to do this for > multimedia/motion? Should've looked before hitting "Send": * Fix ioctl sign-extension warning on FreeBSD https://github.com/Motion-Project/motion/pull/393 C. -- BOFH excuse #101: Collapsed Backbone