From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751010AbdLaJSR (ORCPT ); Sun, 31 Dec 2017 04:18:17 -0500 Received: from mail-oi0-f45.google.com ([209.85.218.45]:44742 "EHLO mail-oi0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750724AbdLaJSN (ORCPT ); Sun, 31 Dec 2017 04:18:13 -0500 X-Google-Smtp-Source: ACJfBosM/Z3ZQrq2qy5KKsdmM+biDEjzhwvE8OAjbzzKjBkH9PANyDqYSulRMSXKzCV/LWsxiG+S0rw0eMUs6y/6FSA= MIME-Version: 1.0 In-Reply-To: References: <001a1137452496ffc305617e5fe0@google.com> <20171231005220.GD22042@localhost.localdomain> <20171231022524.GE22042@localhost.localdomain> From: Willem de Bruijn Date: Sun, 31 Dec 2017 10:17:32 +0100 Message-ID: Subject: Re: general protection fault in skb_segment To: Xin Long Cc: Marcelo Ricardo Leitner , syzbot , David Miller , LKML , linux-sctp@vger.kernel.org, Network Development , Neil Horman , syzkaller-bugs@googlegroups.com, Vlad Yasevich Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> and with the reproducer, got: >> [ 54.255469] Bogus gso_type: 7 >> [ 54.258801] Bogus gso_size: 63464 >> [ 54.262532] ------------[ cut here ]------------ >> [ 54.267703] syz0: caps=(0x00000800000058c1, 0x0000000000000000) len=32 data_len=0 gso_size=63464 gso_type=7 ip_summed0 >> [ 54.279777] WARNING: CPU: 1 PID: 13005 at /root/linux/net/core/dev.c:2600 skb_warn_bad_offload+0xd6/0xec > I couldn't reproduce this call trace on net-next, maybe it's been fixed by: > commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada > Author: Willem de Bruijn > Date: Tue Dec 12 11:39:04 2017 -0500 > > net: avoid skb_warn_bad_offload on IS_ERR Yes, I forgot to mention that that has been fixed in net-next. It does not address the crash, but does suppress the gratuitous warning once we make segmentation return with error for bad packets like these. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Willem de Bruijn Date: Sun, 31 Dec 2017 09:17:32 +0000 Subject: Re: general protection fault in skb_segment Message-Id: List-Id: References: <001a1137452496ffc305617e5fe0@google.com> <20171231005220.GD22042@localhost.localdomain> <20171231022524.GE22042@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Xin Long Cc: Marcelo Ricardo Leitner , syzbot , David Miller , LKML , linux-sctp@vger.kernel.org, Network Development , Neil Horman , syzkaller-bugs@googlegroups.com, Vlad Yasevich >> and with the reproducer, got: >> [ 54.255469] Bogus gso_type: 7 >> [ 54.258801] Bogus gso_size: 63464 >> [ 54.262532] ------------[ cut here ]------------ >> [ 54.267703] syz0: caps=(0x00000800000058c1, 0x0000000000000000) len2 data_len=0 gso_sizec464 gso_type=7 ip_summed0 >> [ 54.279777] WARNING: CPU: 1 PID: 13005 at /root/linux/net/core/dev.c:2600 skb_warn_bad_offload+0xd6/0xec > I couldn't reproduce this call trace on net-next, maybe it's been fixed by: > commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada > Author: Willem de Bruijn > Date: Tue Dec 12 11:39:04 2017 -0500 > > net: avoid skb_warn_bad_offload on IS_ERR Yes, I forgot to mention that that has been fixed in net-next. It does not address the crash, but does suppress the gratuitous warning once we make segmentation return with error for bad packets like these.