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=-5.7 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_PASS,URIBL_BLOCKED autolearn=ham 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 9FBC1C43387 for ; Thu, 3 Jan 2019 13:07:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 684D320815 for ; Thu, 3 Jan 2019 13:07:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730097AbfACNHE (ORCPT ); Thu, 3 Jan 2019 08:07:04 -0500 Received: from mail-io1-f71.google.com ([209.85.166.71]:46651 "EHLO mail-io1-f71.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727067AbfACNHE (ORCPT ); Thu, 3 Jan 2019 08:07:04 -0500 Received: by mail-io1-f71.google.com with SMTP id o22so39408701iob.13 for ; Thu, 03 Jan 2019 05:07:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=M1VjWxMANHeYRKUGYAlmpP6IziprCXFxryyqqAcQm3g=; b=ePxodYReMBTacXg6a/8ZZpCgwDEtvAaAZYn0n6dT4gDpzK1R1JxWqWydncSiT51MKI JjctB220j3BElhnPBQtqZP74CpH+uV274Lt8WEF92Ht0OqC/r90+sm6dX8L6O50MBGSq g2GFDdVWiwMPZyg2h1qug+p7Zy1bZ6TCF+pKys0lttwedsbt4NLweXcF1uSQhfdE0Od0 Lq/VW+azQek/imORzjdiIf7KqP5V+v2It4kLL63kEQafl3jZ3apMGAOJB/Ls1L9BYDaT u0IV0zByWiNniGb6zbgveozWm/13y9bqtd53G6vEHwUUrw1lWquXDNN5mPhiJJTinXFy i72w== X-Gm-Message-State: AA+aEWbZ9eLAS6eDNUTJShfrn3VucLt08DTpxT1vQ0C5gbL++5/M2y+I 82Y6ODNDa3B5PmVe4WcZ/F86TccbNink21dryEQ8fF5kLNMI X-Google-Smtp-Source: AFSGD/UzDXG2Bt168iaUWBnMUuXqjvPGJzjcTITOCDoydy+J/SSut+hSlSu6xQaRHKKkq33KZ2VIH1ddzBXSYMBK7Tmmjq613l8e MIME-Version: 1.0 X-Received: by 2002:a02:6006:: with SMTP id i6mr37057431jac.6.1546520823412; Thu, 03 Jan 2019 05:07:03 -0800 (PST) Date: Thu, 03 Jan 2019 05:07:03 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000513fb7057e8d7013@google.com> Subject: kernel panic: stack is corrupted in udp4_lib_lookup2 From: syzbot To: davem@davemloft.net, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following crash on: HEAD commit: 195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12245d8f400000 kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7 dashboard link: https://syzkaller.appspot.com/bug?extid=4ad25edc7a33e4ab91e0 compiler: gcc (GCC) 8.0.1 20180413 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com protocol 88fb is buggy, dev hsr_slave_1 protocol 88fb is buggy, dev hsr_slave_0 protocol 88fb is buggy, dev hsr_slave_1 FAT-fs (loop0): invalid media value (0x00) FAT-fs (loop0): Can't find a valid FAT filesystem Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: udp4_lib_lookup2+0x7ea/0x7f0 net/ipv4/udp.c:455 CPU: 1 PID: 17960 Comm: syz-executor2 Not tainted 4.20.0+ #176 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: Kernel Offset: disabled Rebooting in 86400 seconds.. --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot.