From: syzbot ci <syzbot+ci881631e3b1154987@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list
Date: Thu, 25 Sep 2025 12:03:14 -0700 [thread overview]
Message-ID: <68d591f2.050a0220.25d7ab.005c.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list
https://lore.kernel.org/all/20250925143312.149623-1-kartikey406@gmail.com
* [PATCH] hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list
and found the following issue:
WARNING: lock held when returning to user space in hugetlb_vmdelete_list
Full report is available here:
https://ci.syzbot.org/series/f0860e54-5be0-4511-bb04-fbd5a7d7a4c7
***
WARNING: lock held when returning to user space in hugetlb_vmdelete_list
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 07e27ad16399afcd693be20211b0dfae63e0615f
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/f58f7b55-7489-4b00-ae8d-a748a39e1223/config
C repro: https://ci.syzbot.org/findings/7a1b33ec-cf07-4a12-8dd6-bd9edef58501/c_repro
syz repro: https://ci.syzbot.org/findings/7a1b33ec-cf07-4a12-8dd6-bd9edef58501/syz_repro
================================================
WARNING: lock held when returning to user space!
syzkaller #0 Not tainted
------------------------------------------------
syz.0.17/5990 is leaving the kernel with locks still held!
1 lock held by syz.0.17/5990:
#0: ffff8880218488e8 (&resv_map->rw_sema){+.+.}-{4:4}, at: hugetlb_vmdelete_list+0x67/0x230 fs/hugetlbfs/inode.c:490
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[akpm@linux-foundation.org david@redhat.com kartikey406@gmail.com linux-kernel@vger.kernel.org linux-mm@kvack.org mike.kravetz@oracle.com muchun.song@linux.dev osalvador@suse.de syzbot@syzkaller.appspotmail.com]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-09-25 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 19:03 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-25 19:23 [moderation/CI] Re: hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list syzbot ci
2025-09-25 21:04 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68d591f2.050a0220.25d7ab.005c.GAE@google.com \
--to=syzbot+ci881631e3b1154987@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.