From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 499D5C5B57D for ; Fri, 5 Jul 2019 07:54:54 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id CB26D218BB for ; Fri, 5 Jul 2019 07:54:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="vancLj2E" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CB26D218BB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2B00A1B998; Fri, 5 Jul 2019 09:54:53 +0200 (CEST) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) by dpdk.org (Postfix) with ESMTP id 67AA31B96E for ; Fri, 5 Jul 2019 09:54:52 +0200 (CEST) Received: by mail-lj1-f175.google.com with SMTP id a21so8355300ljh.7 for ; Fri, 05 Jul 2019 00:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=g1QUQ2wn4cFzytkf5BJovH3oGx4lI8Wy7SAWFyFo5CY=; b=vancLj2EzQZF4g2P6rmE12vZT6Pqri+A9rp28Cx2+I62+fY4429feAfWQZHWdTKV1/ 73LpXqTUieCa+LSPzqCcNuVQ0y/+1vIqWfffaGbk55kURn1IWTzJe+wsFB0vL4qV9gJf adVXJacz5yHsXInwx0245Hlbfma21bEfFtlG37Qh0DGd5f5+6IB4JxO1UTMhc6d/s7fD gkinNN0Hiq1n5MLCuAsAkDlVsZQif4LcLpTM4h+1VMTs2Jtk4sKtLNy4D1RCmPTc54Um zecAWbddHF9HGzHMboSQz7ApPGuJTDfKl9AFLQK1XlKe0Yaz3QvS2pUGWx/P8tSYZb9y OWOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=g1QUQ2wn4cFzytkf5BJovH3oGx4lI8Wy7SAWFyFo5CY=; b=QWi6I6MUeRkecshsleWVXtPQrqLP/tGB9gVcaF11Hmutc0EKpgy0TorEeTQ+TUzRVo 8XguscIaWU7MBBzT5x98bX/xd8dK5ggP2DrBgRBOq7dx9tPjQfw2Qb8qYZXuv9eKahLA nCHc2ejSQlzScvyUcgNDBzqWYWwapdPzzJRYImsbyHtI+k6tkSP2JYFxYG6Fa0x2xHsE ueaCJBpaEX75Vez8ru3pYvwCwvLoEoRfXvobON2tXIZ+tEZTGTVLRbjq5wWfBTplCYUH 1dbdbaxUCJUPkFdHru96wr/zZvVtIh+6lRIzi0WVUbwWy44OKL3CEEWL97xwSNhLSQaS jXCQ== X-Gm-Message-State: APjAAAU8ZwdLeddT74BTF+vJ0fkF+k701DHPZxhKFoEPuXBXdjvajOlh gp+56QG2r3ZlIr6tLImFaG2FOb/AyHD/h+IwwdQ= X-Google-Smtp-Source: APXvYqzyazYcYkc1yMdejc3HuIC9Rpw1uI8e89Y8ShWf+yFuJ6tnW3JsJt+DFnSWAoEczZCqbmhY34iRmfShq6IUZHs= X-Received: by 2002:a2e:8849:: with SMTP id z9mr1326380ljj.203.1562313291870; Fri, 05 Jul 2019 00:54:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: chetan bhasin Date: Fri, 5 Jul 2019 13:24:40 +0530 Message-ID: To: "Dey, Souvik" Cc: "dev@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] kernel crash with DPDK 18.11 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Souvik, I am also facing this issue on DPDK 17.11.4 but not sure whether it is because of fragmented traffic or not. Are you able to get the direction regarding this issue? Can you please guide. Thanks, Chetan Bhasin On Sat, Jun 15, 2019 at 12:00 AM Dey, Souvik wrote: > Hi All, > I am using DPDK 18.11 with linux kernel 4.19.28. I have kni > devices created and I can see a crash in the kernel with ipv6/v4 fragmented > packets. Does anyone seen this already or is there any fixes/patches > available for this . > > Snippet of kernel panic > > > Message from syslogd@vsbc1 at Jun 14 04:52:05 ... > > kernel:[ 6815.672497] rte_kni: kni_net_rx_normal > kernel:[ 6815.672497] skbuff: skb_over_panic: text:0000000024f44e9b > len:3024 put:1518 head:000000002a1b576a data:00000000cec907b4 tail:0xc12 > end:0x980 dev: > > Message from syslogd@vsbc1 at Jun 14 04:52:05 ... > kernel:[ 6815.672497] skbuff: skb_over_panic: text:0000000024f44e9b > len:3024 put:1518 head:000000002a1b576a data:00000000cec907b4 tail:0xc12 > end:0x980 dev: > > Message from syslogd@vsbc1 at Jun 14 04:52:06 ... > kernel:[ 6815.854134] Kernel panic - not syncing: Fatal exception > > Message from syslogd@vsbc1 at Jun 14 04:52:06 ... > kernel:[ 6815.854134] Kernel panic - not syncing: Fatal exception > -- > Regards, > Souvik > > > > ----------------------------------------------------------------------------------------------------------------------- > Notice: This e-mail together with any attachments may contain information > of Ribbon Communications Inc. that > is confidential and/or proprietary for the sole use of the intended > recipient. Any review, disclosure, reliance or > distribution by others or forwarding without express permission is > strictly prohibited. If you are not the intended > recipient, please notify the sender immediately and then delete all > copies, including any attachments. > > ----------------------------------------------------------------------------------------------------------------------- >