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 879A8C433F5 for ; Sat, 1 Oct 2022 14:26:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229660AbiJAO0o (ORCPT ); Sat, 1 Oct 2022 10:26:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229464AbiJAO0l (ORCPT ); Sat, 1 Oct 2022 10:26:41 -0400 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D9C643E69 for ; Sat, 1 Oct 2022 07:26:40 -0700 (PDT) Received: by mail-io1-f70.google.com with SMTP id u9-20020a5edd49000000b006a0f03934e9so4513061iop.4 for ; Sat, 01 Oct 2022 07:26:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=Je8P4OmrMwwcd92gAPOyOtWipPfjQ5H1rtE8DydHvww=; b=Thk7amMffEMzz1ZyDxjC1cAIMK8T5t40KgL/LcDt0qSx1oKMffRXUlFKX/tEEZyEHM pscKjUYepM43WyNBNN94NTr48fs7GOuOoZeoJAHcB5WJ3DUU5A9nHywve2EuFK2ZfMYy Dy5C+BujrAeeRle6p5qxdP/oKeNqoO/LMFFeZQrbKGZtUqejXGZWi0T1VTWeRT8FHHJI 01igC2bRa5MjvuUhDFabRbMeQ8KYpwI0f/bHvUQJEuMZrmlOnOwwsV4tyrHJ4SDLy2wd tKHNnUdNPSetp12cg1LPQ5GJEYnhMBC/4FKLx9YKLawHbZTQJ//Riax64AlOPUrZDw18 o07Q== X-Gm-Message-State: ACrzQf2bP952BSlactzSIQZbRNtVHvv5nALX5ilnBxWquG+dnHcd4/Ki EfEMcuX50XaVk8o1mjRv6Z3vAk2+KAJdrKcdMAezXkZ7CHx8 X-Google-Smtp-Source: AMsMyM6yjQnXyMZg6FdGm3jJkyCZ8gcr1C+5wXJunpfQ3BcRsspMMODg2aYqalBfSkeMFWBu4lcUoRu4C1AoD1R+dkwtfnq58sr/ MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1baf:b0:2f5:a7b0:65a8 with SMTP id n15-20020a056e021baf00b002f5a7b065a8mr6085915ili.227.1664634400029; Sat, 01 Oct 2022 07:26:40 -0700 (PDT) Date: Sat, 01 Oct 2022 07:26:40 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000001850d105e9f9e6de@google.com> Subject: [syzbot] WARNING: lock held when returning to user space in ieee80211_change_mac From: syzbot To: davem@davemloft.net, edumazet@google.com, johannes@sipsolutions.net, kuba@kernel.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 6627a2074d5c net/smc: Support SO_REUSEPORT git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=10183a70880000 kernel config: https://syzkaller.appspot.com/x/.config?x=d4d64087513b5aa1 dashboard link: https://syzkaller.appspot.com/bug?extid=4ef359e6b423499fa4e1 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/9ecb75606956/disk-6627a207.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1073865fcb40/vmlinux-6627a207.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+4ef359e6b423499fa4e1@syzkaller.appspotmail.com ================================================ WARNING: lock held when returning to user space! 6.0.0-rc6-syzkaller-01407-g6627a2074d5c #0 Not tainted ------------------------------------------------ syz-executor.3/10164 is leaving the kernel with locks still held! 1 lock held by syz-executor.3/10164: #0: ffff888147acaa88 (&local->mtx){+.+.}-{3:3}, at: ieee80211_can_powered_addr_change net/mac80211/iface.c:217 [inline] #0: ffff888147acaa88 (&local->mtx){+.+.}-{3:3}, at: ieee80211_change_mac+0x9b4/0xf40 net/mac80211/iface.c:264 --- This report 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 issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.