From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f80.google.com (mail-io1-f80.google.com [209.85.166.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 31F7018638 for ; Wed, 25 Dec 2024 21:54:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.80 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735163663; cv=none; b=qV+Tbmw8hge2/kbNNnwhG20J5AMZCAEAon/bs73BYstVtOAQRXj5EuPxpdUD57i6+Ezv5lsJENg6ZGtXqMq7FmUiUKzxQZDaMdN4/gv86nS5ZdMY37YMjHA8nZSow2EhlYXRqy6uvPvSyohLjUMTB7EdMCvvPVjm7HGW5g6+aWo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735163663; c=relaxed/simple; bh=64Pc2yv+DfVpQsvUNXXO+waFg2xisBojR+sGmULLJPE=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=doDhuW55MkGcE9l+Inopolo9depS5MUX1QFH3/2xOnA3JfX/L08RCccStntiNYR3NoF0e0PpbRtYeNQ4UyXIo5tplAzUBCq7981/4niajh1CXlbWOW6xvO8Xv10VepYTv2CjZrJXg0TqVt8qiqDh94xzAR3CwS+CHV6In5k2NQY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.80 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f80.google.com with SMTP id ca18e2360f4ac-84730592e44so509312039f.3 for ; Wed, 25 Dec 2024 13:54:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735163661; x=1735768461; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Zw5r7rPgpTNylvvr3KlNlXAbhRcsipIejQSjScxWqYo=; b=JL4pAe0xqiIVZONdPigerQfDhgT/J0gmGyNGKx7Z9r4QwSko+90PcJ6pNgzI3Dzw+1 POZX9RN48qdJDfsRw2yu0gb2TzpcSu9mMZCezUeuVpOLz6LzdYWdO3uKFyeItotIIjGc q/PXhd3ASZ12ZDgZ4xwSep4a6nhW5RITj1Fk6ykhYc2V5v8f2SVGmUjDLxQTZZDB2pc2 k6U+wpzQ1WbxqONgePK4qwOzGKqHpAsC+PpIHTLSmVfIoZRAdWPobK7IYZYZZNwotxo2 bBhvfwP3E+tuJR8HohRx+f1LFcq/WnhJHpmVqO2gyC2q2OFUV+/YHghLXRCOTYD/o4Xm U/Og== X-Forwarded-Encrypted: i=1; AJvYcCXjMRO623gUDNO62cvUwDuN88lAik3ajukV5iVo79f1/M8t3MlktertSr04hPX5nVgKCr4vKjbJlijzxi8=@vger.kernel.org X-Gm-Message-State: AOJu0YwkY+RA1/PwfXPsyu+haIkssvZfQ6GdW0e2+rld0bhnQfsbgx2n gYupMqtg+oHO8TmDZ/BbwfeeAO8uOEHB5a/ZIAgjR7BMX9MTUTHAeBMdoQiimixVKgVI2plmlLG ARlnASf55V2k8mjbDSJIyt5APGSyyvDZ9XKxhSLgoi/UTDjdyeIaB5DA= X-Google-Smtp-Source: AGHT+IH1BZai3wEd4m8TI0qS2Qh2M+WGXIzCpV5CFEB/Dd4N/+5uY6BurNfElCHDERLxIn5kcZ3gvIASSQ2hBbY8OGiKEwJRtpr1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1d9c:b0:3a7:87f2:b010 with SMTP id e9e14a558f8ab-3c2d1aa2b54mr173121305ab.5.1735163661328; Wed, 25 Dec 2024 13:54:21 -0800 (PST) Date: Wed, 25 Dec 2024 13:54:21 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <676c7f0d.050a0220.2f3838.03bb.GAE@google.com> Subject: [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write From: syzbot To: dhowells@redhat.com, linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org, marc.dionne@auristor.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 499551201b5f Merge tag 'arm64-fixes' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=153420c4580000 kernel config: https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769 dashboard link: https://syzkaller.appspot.com/bug?extid=76f33569875eb708e575 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1503ef30580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d33cf8580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/5ee1fc255de9/disk-49955120.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/24f10c9fac9a/vmlinux-49955120.xz kernel image: https://storage.googleapis.com/syzbot-assets/211e35102c2e/bzImage-49955120.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+76f33569875eb708e575@syzkaller.appspotmail.com netdevsim netdevsim0 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 kafs: addr_prefs: Too many elements in string ================================================ WARNING: lock held when returning to user space! 6.13.0-rc3-syzkaller-00209-g499551201b5f #0 Not tainted ------------------------------------------------ syz-executor133/5823 is leaving the kernel with locks still held! 1 lock held by syz-executor133/5823: #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: afs_proc_addr_prefs_write+0x2bb/0x14e0 fs/afs/addr_prefs.c:388 --- 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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup