From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 26 07:28:15 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA859106564A for ; Tue, 26 Oct 2010 07:28:15 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 26E518FC12 for ; Tue, 26 Oct 2010 07:28:14 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA21010; Tue, 26 Oct 2010 10:28:11 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PAdx5-0002aS-2p; Tue, 26 Oct 2010 10:28:11 +0300 Message-ID: <4CC6830A.10701@icyb.net.ua> Date: Tue, 26 Oct 2010 10:28:10 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.11) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.5 MIME-Version: 1.0 To: Selphie Keller References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Konstantin Belousov Subject: Re: SYSCALL_MODULE() macro and modfind() issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2010 07:28:15 -0000 on 26/10/2010 01:01 Selphie Keller said the following: > hi fbsd-hackers, > > Noticed a issue in 8.1-release, 8.1p1-release and 8.1-stable > amd64/i386, to where modfind() will no longer find pmap_helper for the > /usr/ports/sysutils/pmap port, or other syscall modules using > SYSCALL_MODULE() macro. > The issue is that modfind() function no longer finds any modules using > SYSCALL_MODULE() macro to register the kernel module. Making it > difficult for userland apps to call the syscall provided. modfind() > always returns -1 which prevents modstat() from getting the required > information to perform the syscall. > > Also tested, the demo syscall module: After commit r205320 and, apparently, its MFC you need to prefix the module with "sys/". For example: modstat(modfind("sys/syscall"), &stat); P.S. Perhaps a KPI breakage in a stable branch? -- Andriy Gapon