From owner-freebsd-net@freebsd.org Wed Dec 9 10:02:58 2015 Return-Path: Delivered-To: freebsd-net@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 D14579D5C3B for ; Wed, 9 Dec 2015 10:02:58 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6BC01C44; Wed, 9 Dec 2015 10:02:58 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by pacwq6 with SMTP id wq6so27467093pac.1; Wed, 09 Dec 2015 02:02:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ATs/QYSLrIh0HYRIE2g60aGMXHMO1ej9DhTQsLEuHY0=; b=j/z26oTmsLHYhG7Ev4/rY4q+BclNl83rTDlEdu9ppbNyRhDuXKUFdc3KQJ46LIXBz2 5RVKPMA61GdtZtH1WR2PQvSC8jSWme4jxgSHKUqzlLcSYU3v/yNrpfiNFBRSY9AraM9t Q5M6RXWuipoQ94NmATl64v73gawBPzfMTIGYDYAeaBWeyexjUCOXmgWVnWZ8Hx7kigFI 67wgYIJuz7a+rPhG+old3/1katvhwq0/i8W1mwFoBW8XBu32EPp04kQewnvq2kAytP99 ctxrcAdkgVOqI6sUcI+LB7Gt9wE+dtFPJaLbdbNERxJ3oDORexwufgxKLddJNUIAUuMC sm4A== X-Received: by 10.66.219.228 with SMTP id pr4mr6370155pac.99.1449655378271; Wed, 09 Dec 2015 02:02:58 -0800 (PST) Received: from ?IPv6:2001:44b8:31ae:7b01:e88a:629d:a199:b333? (2001-44b8-31ae-7b01-e88a-629d-a199-b333.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:e88a:629d:a199:b333]) by smtp.gmail.com with ESMTPSA id dz6sm10529960pab.19.2015.12.09.02.02.55 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Dec 2015 02:02:57 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Multiple cores/race conditions in IPv6 RA References: <50cff74ea38f155ae616cf49f5ffb5ae@m.nitrology.com> <5667EA3A.8050200@FreeBSD.org> <5667EC45.2050808@FreeBSD.org> <5667ED4C.90405@FreeBSD.org> To: "Andrey V. Elsukov" , Jason , freebsd-net@freebsd.org Cc: Mark Johnston , kevin.bowling@kev009.com, hiren@strugglingcoder.info From: Kubilay Kocak Message-ID: <5667FC48.5090507@FreeBSD.org> Date: Wed, 9 Dec 2015 21:02:48 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0 MIME-Version: 1.0 In-Reply-To: <5667ED4C.90405@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2015 10:02:58 -0000 On 9/12/2015 7:58 PM, Andrey V. Elsukov wrote: > On 09.12.15 11:54, Kubilay Kocak wrote: >>> some time ago Mark Johnston has published there the patch related to >>> this problem: >>> https://lists.freebsd.org/pipermail/freebsd-net/2013-February/034682.html >>> >>> Maybe Mark has something to say about it. >>> >> >> Is it worth creating an issue report to track/resolve this, with 10.3 >> coming up? > > This problem exists since 4.x-5.x, so, I don't think that creating a > report will automatically resolve it :) > Not automatically no. But perhaps never being tracked has contributed to its non-resolution?