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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8E280C7619A for ; Sat, 8 Apr 2023 08:06:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230091AbjDHIGZ (ORCPT ); Sat, 8 Apr 2023 04:06:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229660AbjDHIGW (ORCPT ); Sat, 8 Apr 2023 04:06:22 -0400 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4D875B76C for ; Sat, 8 Apr 2023 01:06:21 -0700 (PDT) Received: by mail-io1-f69.google.com with SMTP id d132-20020a6bb48a000000b00758cfdd36c3so561803iof.0 for ; Sat, 08 Apr 2023 01:06:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680941180; x=1683533180; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NLKTEBYGBUcdC4+NrJFvw8GqolXrkHDp+UdkTTsKyQo=; b=YHMfXBGBqGF7vnyiwfegRzrPr5nCj3WqQhYpM9+wy5en4aDsgtsBHQZE/HdFCQhM9q HBz6aCWEtdIyJ5CtrgvHBtuDWK+mtrjp4JV3Qm9Bv2yuSwZeJ2xnBm1axUcki5lqldgT zTW5DVxgOkEREm/T73/lNizJvBPRGPwuT8P7LvF9gIuQJnfPmsnW2784bMEVnXN45suo Ix3pIahSjinwP1U+ptGSRroNPfRUhOCe+HaRvHjgrdBWpOIYIG6XS3DjdAjgkUXnI3gf +g0Z9LF2PYCJyKVzDXNx3FBvAA4IFCM6WD9S+zdDqLzK5ZiQm5tja2VoatCnIMB5E7gp vjZg== X-Gm-Message-State: AAQBX9dpudi9+PpLnCiISGu6uTBOpDq0TXc3LNBwuvawLvrYPkMMelas gtxKC0XksNRgIHHOURkCAzTWq+agzPJjNLd77TL1SpWklr/9 X-Google-Smtp-Source: AKy350a2iulIYkLY7Odfq/IxdjlQjY9IPJrnVb7mS/3bxUH66cJ7i/IRyHiDovCenDnd0N+SbFS4SK4yFeNwQCGhQT33DB2GBs/5 MIME-Version: 1.0 X-Received: by 2002:a05:6602:2d94:b0:758:f2d3:7fa1 with SMTP id k20-20020a0566022d9400b00758f2d37fa1mr6767209iow.0.1680941180516; Sat, 08 Apr 2023 01:06:20 -0700 (PDT) Date: Sat, 08 Apr 2023 01:06:20 -0700 In-Reply-To: <20230408075220.1312-1-hdanton@sina.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000f403b005f8ce9d9a@google.com> Subject: Re: [syzbot] [net?] WARNING in cleanup_net (2) From: syzbot To: hdanton@sina.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: WARNING in cleanup_net __sock_create+0x380/0x850 net/socket.c:1545 __smc_create net/smc/af_smc.c:3267 [inline] smc_create+0x1fc/0x2d0 net/smc/af_smc.c:3284 __sock_create+0x380/0x850 net/socket.c:1545 sock_create net/socket.c:1596 [inline] __sys_socket_create net/socket.c:1633 [inline] __sys_socket_create net/socket.c:1618 [inline] __sys_socket+0x133/0x250 net/socket.c:1661 __do_sys_socket net/socket.c:1674 [inline] __se_sys_socket net/socket.c:1672 [inline] __x64_sys_socket+0x73/0xb0 net/socket.c:1672 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11 at lib/ref_tracker.c:39 spin_unlock_irqrestore include/linux/spinlock.h:405 [inline] WARNING: CPU: 0 PID: 11 at lib/ref_tracker.c:39 ref_tracker_dir_exit+0x3a2/0x600 lib/ref_tracker.c:38 Modules linked in: CPU: 0 PID: 11 Comm: kworker/u4:1 Not tainted 6.3.0-rc3-syzkaller-00148-gf33642224e38-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023 Workqueue: netns cleanup_net RIP: 0010:ref_tracker_dir_exit+0x3a2/0x600 lib/ref_tracker.c:39 Code: 0f 84 c3 fe ff ff e8 2d 3d 44 fd 44 89 ff e8 c5 f9 ff ff e9 b1 fe ff ff e8 1b 3d 44 fd 48 8b 74 24 10 4c 89 ef e8 de 99 c6 05 <0f> 0b e8 07 3d 44 fd 49 8d 6d 44 be 04 00 00 00 48 89 ef e8 e6 4e RSP: 0018:ffffc90000107c00 EFLAGS: 00010246 RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000001 RDI: 0000000000000001 RBP: ffff88802bb9bb90 R08: 0000000000000001 R09: ffffffff914d9c7f R10: 0000000000000001 R11: 0000000000000000 R12: ffff88802bb9bb90 R13: ffff88802bb9bb40 R14: ffff88802bb9bb90 R15: ffff88802629d108 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb01fad35c0 CR3: 00000000296c4000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: net_free net/core/net_namespace.c:447 [inline] net_free net/core/net_namespace.c:441 [inline] cleanup_net+0x8bb/0xb10 net/core/net_namespace.c:634 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390 worker_thread+0x669/0x1090 kernel/workqueue.c:2537 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 Tested on: commit: f3364222 ptp_qoriq: fix memory leak in probe() git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git console output: https://syzkaller.appspot.com/x/log.txt?x=16194d79c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=ea09b0836073ee4 dashboard link: https://syzkaller.appspot.com/bug?extid=7e1e1bdb852961150198 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 patch: https://syzkaller.appspot.com/x/patch.diff?x=15e5feb5c80000