Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2653657yba; Mon, 22 Apr 2019 10:32:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqyErvViIkuCvn6Vov+2hVJF03np/aX/COspnWbMaEV6bHNZ3kMDIN8uSlatGvMsU0cKoBZ4 X-Received: by 2002:a63:8f49:: with SMTP id r9mr13573993pgn.306.1555954346322; Mon, 22 Apr 2019 10:32:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555954346; cv=none; d=google.com; s=arc-20160816; b=YO9rF1QPqr4pIWg/VELQKQmozIRBsf3YZuLfr/eLPCism+e6bPaNaXuvHJPI88gEj+ ywspwXebdha93+SuFrvcd4Q3RvuSy4CkSAIDQdWO7X/QzYU+fb0VI70qogP/FWmn/5Hu kimhIjoZyec4x79VlFIvKxoO71PIhGpcFjAn3WBDs5Tvmc032yR6iIhG18BuXm24p6GO LrMmAZOrFoFTSNKzaKZW5EWEw3GS2KlR7z7bBGOn1goQHqurjIK/849Dw+YorkIq0z9S EC3XpOx8WN1Q+/HuNqLfhWeOMWumayhwil1zYq+0P2XTPjP118SY11/z1XresP0YMst/ YHIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=TTX2xJN3Ewd2sQKUXiVdXt9ctTIBZn8R5gUr0mqD8X0=; b=OHn4/eDNkHpaKZLbYEqU+/TXoUxcfgToVosusGeAest6JekH8sXybArU7Vb0Vir7n6 1pJxtNKRU393YhH6SkCggICP2ZjdJECWwAv4tXC/xoTzArC68WblNLjSin5/MueVuGrW DsfdbF+JsTfEtZl1jLfFV05eTZtqoEVN5nyYH/9Pv8xlK/Trfg4dp13t1hqy32e0EORk kTq3J+Yzw9bJRGOpW/3iG8WspY0iRDLLt64qQtTcjpxqh6DSIOX8rOdJXM6NWwHOFg4j /x2XNsW0mj8dxx0+07wmQBsatb2//kzWDnG3C5kH0qPuyMcRKodHWL9uaI7agMGUUsKF 5HMg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m17si12584567pgi.514.2019.04.22.10.32.09; Mon, 22 Apr 2019 10:32:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727818AbfDVR1f (ORCPT + 99 others); Mon, 22 Apr 2019 13:27:35 -0400 Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:52046 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726587AbfDVR1f (ORCPT ); Mon, 22 Apr 2019 13:27:35 -0400 Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.89) (envelope-from ) id 1hIcj6-0002Na-KD; Mon, 22 Apr 2019 19:27:32 +0200 Date: Mon, 22 Apr 2019 19:27:32 +0200 From: Florian Westphal To: Andreas Hartmann Cc: Florian Westphal , Pablo Neira Ayuso , linux-kernel@vger.kernel.org Subject: Re: [PATCH 4.19 13/99] netfilter: nf_conncount: fix argument order to find_next_bit Message-ID: <20190422172732.sneybhuwrreb7g2u@breakpoint.cc> References: <20190121134913.924726465@linuxfoundation.org> <20190121134914.421023706@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andreas Hartmann wrote: > Since 4.19.17, I'm facing problems during streaming of videos I've never seen before. This means: > > - video from internet stutters although enough data flow can be seen in bmon. > - gpu is locked: > radeon 0000:0a:00.0: ring 0 stalled for more than 14084msec > radeon 0000:0a:00.0: GPU lockup (current fence id 0x0000000000053ed7 last fence id 0x0000000000053f0f on ring 0) > - The connection of videos streamed locally by the machine for a TV suddenly breaks (upnp - serviio as server). > > After very long time of testing, I detected, that removing the complete patch series for 4.19.17 regarding netfilter: nf_conncount makes the problem disappear. > > Please remove / fix this patchset! The state in 4.19.y is same as in mainline. Could you at least tell us how you're using nf_conncount (nf/iptables rules)? Could you test with debugging (KASAN, CONFIG_PROVE_RCU etc). enabled? I'm really surprised about this report, before the backport nf_conncount caused frequent kernel crashes, how does reverting even work...?