From owner-freebsd-net@FreeBSD.ORG Tue Mar 24 15:18:40 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CFD7E7C for ; Tue, 24 Mar 2015 15:18:40 +0000 (UTC) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 5C820792 for ; Tue, 24 Mar 2015 15:18:39 +0000 (UTC) Received: from lgwl-lstewart2.corp.netflix.com (dhcp-ac72.meeting.ietf.org [31.133.172.114]) by lauren.room52.net (Postfix) with ESMTPSA id C96127E81E; Wed, 25 Mar 2015 02:09:45 +1100 (EST) Message-ID: <55117E37.80301@swin.edu.au> Date: Tue, 24 Mar 2015 10:09:43 -0500 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "Eggert, Lars" Subject: Re: siftr buildkernel failure? References: <46a9d8ac6681429b81502c09b8ff4e18@GSP-EX02.ds.swin.edu.au> In-Reply-To: <46a9d8ac6681429b81502c09b8ff4e18@GSP-EX02.ds.swin.edu.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.4 required=5.0 tests=DNS_FROM_AHBL_RHSBL, UNPARSEABLE_RELAY autolearn=no version=3.3.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: "freebsd-net@freebsd.org" , hiren panchasara X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2015 15:18:40 -0000 On 03/24/15 07:49, Eggert, Lars wrote: > Anyone else seeing this on -current right now? > > /usr/home/elars/src/sys/modules/siftr/../../netinet/siftr.c:493:7: error: data argument not used by format string [-Werror,-Wformat-extra-args] > pkt_node->flowid, > ^ I didn't look at enough context when reviewing r280233 and missed the bug. Should be fixed in r280441. Thanks for the report and apologies for the hassle. Cheers, Lawrence