From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH net v2] netfilter: nat: cope with negative port range Date: Wed, 14 Feb 2018 04:28:26 -0800 Message-ID: <1518611306.3715.193.camel@gmail.com> References: <184e6d2a1ab2e474c12be6e9819d7cf2cc846f26.1518606740.git.pabeni@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Pablo Neira Ayuso , Florian Westphal , "David S. Miller" , netfilter-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com To: Paolo Abeni , netdev@vger.kernel.org Return-path: Received: from mail-it0-f44.google.com ([209.85.214.44]:50390 "EHLO mail-it0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967547AbeBNM2a (ORCPT ); Wed, 14 Feb 2018 07:28:30 -0500 In-Reply-To: <184e6d2a1ab2e474c12be6e9819d7cf2cc846f26.1518606740.git.pabeni@redhat.com> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Wed, 2018-02-14 at 12:13 +0100, Paolo Abeni wrote: > syzbot reported a division by 0 bug in the netfilter nat code: ... > Adding the relevant check at parse time could break existing > setup, moreover we would need to read/write such values atomically > to avoid possible transient negative ranges at update time. I do not quite follow why it is so hard to add a check at parse time. Breaking buggy setups would not be a concern I think.