From owner-freebsd-stable@FreeBSD.ORG Thu Aug 29 10:25:07 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0A10238C; Thu, 29 Aug 2013 10:25:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 202022864; Thu, 29 Aug 2013 10:25:05 +0000 (UTC) Received: from porto.starpoint.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 NAA25062; Thu, 29 Aug 2013 13:25:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VEzPU-0002oi-6a; Thu, 29 Aug 2013 13:25:04 +0300 Message-ID: <521F215C.9080900@FreeBSD.org> Date: Thu, 29 Aug 2013 13:24:28 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jase Thew , Toomas Aas Subject: Re: [HEADS UP] change in devfs path matching logic References: <51F28A33.7040209@FreeBSD.org> <52176C7B.4070701@FreeBSD.org> <20130824230324.12371xhs3clidbi8@webmail.raad.tartu.ee> <521E3394.5050000@FreeBSD.org> <521EFCAB.5030200@FreeBSD.org> In-Reply-To: <521EFCAB.5030200@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2013 10:25:07 -0000 on 29/08/2013 10:47 Andriy Gapon said the following: > It looks like I should have done more investigation on the state of devfs in > stable/8 before MFC-ing the change. There are several earlier big commits that > have not been MFC-ed. > So, now I can either revert the MFC and be done with it. > Or we can try to investigate the crash and see if it's easy to fix it. In fact, I am not sure but I hope that the fix could be as simple as MFC-ing r211847: http://svnweb.freebsd.org/base?view=revision&revision=211847 http://svnweb.freebsd.org/base/head/sys/fs/devfs/devfs_vnops.c?view=patch&r1=211847&r2=211846&pathrev=211847 -- Andriy Gapon