From owner-freebsd-current@FreeBSD.ORG Fri Aug 30 01:57:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8D65EEBC for ; Fri, 30 Aug 2013 01:57:13 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 69EE12A15 for ; Fri, 30 Aug 2013 01:57:13 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id md4so1206285pbc.30 for ; Thu, 29 Aug 2013 18:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eenTw8izQ+mTiZDOldWbyhEhnh+Y1xCD7yQ9u3IV52E=; b=m+hxcjSRbFtg6vigWXCGUpav9S+fM1pnBBwdCJp7u6w8SvXtsUWLgQ3dZRhKY/iPSz PLIRVR1E/2Lx0yKZH4fuNrm3V5Cv/mVB4EcKLxlpy8406Qpo5ASiGIGZp4iAwd3CHDI/ dshRJUHFegJqnCboAV0r2HIzuuF4yGbnyVP9uD514dyJRrNuj2CNMr1mSisPe2JPEEkq LC4efG7ArR+r7WMBJSHG1cEe5nnFRc/WN+gzpKebhI3BB5lXqGbSoPW/N0xKLIQHqrF7 VgzQDFZj+NoPnITQx5qjp8k6X4wc/RkDvSHRrt/xVIrEuTMRjwmhUKV4XsgiyTp+gsWm 1odg== MIME-Version: 1.0 X-Received: by 10.66.233.37 with SMTP id tt5mr7511272pac.95.1377827833104; Thu, 29 Aug 2013 18:57:13 -0700 (PDT) Received: by 10.68.212.138 with HTTP; Thu, 29 Aug 2013 18:57:13 -0700 (PDT) Date: Thu, 29 Aug 2013 21:57:13 -0400 Message-ID: Subject: if_tap(4) being inconsistent between svn updates From: Aryeh Friedman To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2013 01:57:13 -0000 I track -CURRENT (mostly for bhyve) and have found between updates that if_tap often requires different calling semantics to work... sometimes it needs and IP ad sometimes it doesn't it s the primary problem (on the same update it is consitent is only after installing new updates [not all new ones] this happens)... my guess is there is somehow some interaction between it and the rest of the kernel where the rest of the kernel sometimes requires and IP and sometimes not