From owner-freebsd-net@freebsd.org Thu Jan 12 16:40:52 2017 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 18560CAC443 for ; Thu, 12 Jan 2017 16:40:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 AA2C617F6; Thu, 12 Jan 2017 16:40:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id c85so27318415wmi.1; Thu, 12 Jan 2017 08:40:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TtwQB+IP7KpwgzfYZAyEITasAFeFrtabUELC/qkVWYg=; b=QEy8ZJXrDPJ+d5GnY5wV2MNBY7JS5w97bKWt9d+UYeowLPAZtgb0RMKBHvUTDZipcr 04RCbDfHoQH0np86GhP2kkEd4CqOoF8oAUIa7J8sk9O71IdJh4otDWSaSpCVHdsXwgPE l+KlgPFv6Eo5di9FK7Y4UTwdeiuPbkxTLakGtRDJpdSHw8rX/MtNMPkKFt73/UQQzG+I 4MQGUVbTKUgsLdJSMQggTzjTkWChzMIdw0YWrRuT9okqkeBVToJDUB9zEjRGQ17WKS7W GDg2P896ZC+aSuqeKzrznGn8f3XprDuP/hrqz41qnu2eM4Jc4YDAWjNHPrUEsbJXsggc i59A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TtwQB+IP7KpwgzfYZAyEITasAFeFrtabUELC/qkVWYg=; b=RmeWSuE1AysLqsaYqPkTMIv16a3SBk3Nz2miXBDxX3MuKKfMiX/8RIt9f7MZrdduMC p737tXBUNF26AWks2GbmJDzFo0UQXeJfZfLdCq2xaQRFYrNVqXkVGTmgeaEWn5ZTUgj5 MQfRKiDpK97LZ9/xuQ+GcNR8eL+1vvfKnRWwVeBLjjd2N5avO77qm4dZqps8k4cyxVNt c332W0bmNElbHcI7JnQIwHORQ5V6YMXS1sVUMlUL+NIaD9II1tbZ77lu19tBRND6clqg /uhwRwmuI38hS1HMDbp/Js7r6e1xb92x2SC1MukztFr4OiMw/lVnqWsJCHgqk/3OuLI1 eICg== X-Gm-Message-State: AIkVDXKpHiGFIgcP0KmH8zo2c54pmiWuJ3GqWuvPaM3mfg3/Vd+YakhfjmVvJhsvwHy90qWqdoRxKu8hZqPwJw== X-Received: by 10.223.151.138 with SMTP id s10mr7860857wrb.65.1484239249398; Thu, 12 Jan 2017 08:40:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.162 with HTTP; Thu, 12 Jan 2017 08:40:48 -0800 (PST) In-Reply-To: References: <20161128221033.GM55731@strugglingcoder.info> <20161129190509.GO27748@FreeBSD.org> From: Adrian Chadd Date: Thu, 12 Jan 2017 08:40:48 -0800 Message-ID: Subject: Re: FLOWTABLE aka TCP route caching panic To: Jakub Palider Cc: Gleb Smirnoff , FreeBSD Net , hiren panchasara , karels@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 16:40:52 -0000 i can reproduce this daily using flowtable on a wifi enabled PC on -HEAD. -adrian On 12 January 2017 at 06:13, Jakub Palider wrote: > An update: eventually, FLOWTABLE option also resulted in crash with > __rw_lock_hard on FreeBSD release/11.0.0 (also on VM). > This time, however, the backtrace was different, instead of > tcp_output->ip_output->ether_output() chain, it happened in > flowtable_clean_vnet() > > On Wed, Jan 11, 2017 at 10:42 AM, Jakub Palider wrote: > >> On Tue, 29 Nov 2016 11:05:09 -0800 >> Gleb Smirnoff wrote: >> >> > On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote: >> > h> > Hi, >> > h> > I have found that last month (19 Oct) the problem appeared on this >> list, >> > h> > and to my experience it persists, both on VM and bare metal >> installation >> > h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option is >> the only >> > h> > source of this fault happening. It appears on our setup in 80% >> cases within >> > h> > one hour from boot up. >> > h> > From our debugging, it is caused by lock on DESTROYED lock. Did you >> find a >> > h> > solution to this problem? >> > >> > Not yet. >> > >> > I'm pretty sure that reverting my r307234 will fix your crashes. >> However, I still >> > believe that r307234 is a proper way of fixing things, not r300854 which >> just >> > plugged the problem in the nearest place to the crash. But as we all see >> r307234 >> > is definitely missing some code path, which still allows for stale route >> to be >> > referenced. >> > >> > -- >> > Totus tuus, Glebius. >> >> Thank you for your pointer, in helped at some point. The problem >> however returned, especially when under heavy, continuous load. We are >> running 4 iperf3 processes, each having 4 threads, and the machine >> dies after 30-60 minutes of TCP traffic. I am running rS30911112 from >> Nov 24. >> On FreeBSD 11.0-RELEASE this problem (1 full day of testing) was not >> noticed. Could you point to related commits that might also influence >> this behaviour? >> Thanks, >> Jakub >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"