[parent not found: <20260216051808.39072-1-activprithvi@gmail.com>]
[parent not found: <20260216042729.31754-1-activprithvi@gmail.com>]
[parent not found: <20260210140002.27253-1-activprithvi@gmail.com>]
[parent not found: <20260210135257.23957-1-activprithvi@gmail.com>]
[parent not found: <20260210134807.21522-1-activprithvi@gmail.com>]
[parent not found: <20260210134120.18174-1-activprithvi@gmail.com>]
[parent not found: <20260209154456.48661-1-activprithvi@gmail.com>]
[parent not found: <20260209153733.45193-1-activprithvi@gmail.com>]
[parent not found: <20260209150120.31598-1-activprithvi@gmail.com>]
[parent not found: <20260209142936.18000-1-activprithvi@gmail.com>]
* Re: [syzbot] [fs?] possible deadlock in __configfs_open_file
[not found] <20260209142936.18000-1-activprithvi@gmail.com>
@ 2026-02-09 14:46 ` syzbot
0 siblings, 0 replies; 19+ messages in thread
From: syzbot @ 2026-02-09 14:46 UTC (permalink / raw)
To: activprithvi, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
possible deadlock in __configfs_open_file
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/6458 is trying to acquire lock:
ffff88802836c678 (&p->frag_sem){.+.+}-{4:4}, at: __configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
but task is already holding lock:
ffff88802836c678 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff88802836c678 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x218/0x4c0 fs/configfs/file.c:229
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&p->frag_sem);
lock(&p->frag_sem);
*** DEADLOCK ***
May be due to missing lock nesting notation
5 locks held by syz.0.17/6458:
#0: ffff888078dc50b8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2aa/0x380 fs/file.c:1255
#1: ffff88801cbe4420 (sb_writers#12){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:738
#2: ffff888032363888 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x76/0x4c0 fs/configfs/file.c:226
#3: ffff88802836c678 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
#3: ffff88802836c678 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x218/0x4c0 fs/configfs/file.c:229
#4: ffffffff8f65ede8 (target_devices_lock){+.+.}-{4:4}, at: target_core_item_dbroot_store+0x21/0x300 drivers/target/target_core_configfs.c:114
stack backtrace:
CPU: 1 UID: 0 PID: 6458 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
print_deadlock_bug.cold+0xbd/0xca kernel/locking/lockdep.c:3041
check_deadlock kernel/locking/lockdep.c:3093 [inline]
validate_chain kernel/locking/lockdep.c:3895 [inline]
__lock_acquire+0x1287/0x2690 kernel/locking/lockdep.c:5237
lock_acquire kernel/locking/lockdep.c:5868 [inline]
lock_acquire+0x17c/0x330 kernel/locking/lockdep.c:5825
down_read+0x99/0x460 kernel/locking/rwsem.c:1537
__configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
do_dentry_open+0x73e/0x1570 fs/open.c:962
vfs_open+0x82/0x3f0 fs/open.c:1094
do_open fs/namei.c:4637 [inline]
path_openat+0x21dc/0x3120 fs/namei.c:4796
do_filp_open+0x1f7/0x420 fs/namei.c:4823
file_open_name+0x198/0x3b0 fs/open.c:1376
filp_open+0x4b/0x80 fs/open.c:1396
target_core_item_dbroot_store+0x108/0x300 drivers/target/target_core_configfs.c:134
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x302/0x4c0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x6ac/0x1070 fs/read_write.c:686
ksys_write+0x12a/0x250 fs/read_write.c:738
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f3eb239a539
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3eb31fa028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f3eb2605fa0 RCX: 00007f3eb239a539
RDX: 0000000000000fff RSI: 0000200000000000 RDI: 0000000000000003
RBP: 00007f3eb242dee0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3eb2606038 R14: 00007f3eb2605fa0 R15: 00007fff2b6e3ce8
</TASK>
db_root: not a directory: /sys/kernel/config/target/dbroot
Tested on:
commit: 05f7e89a Linux 6.19
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=124dd402580000
kernel config: https://syzkaller.appspot.com/x/.config?x=55c0bf5c4b466402
dashboard link: https://syzkaller.appspot.com/bug?extid=f6e8174215573a84b797
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=149f17fa580000
^ permalink raw reply [flat|nested] 19+ messages in thread
[parent not found: <20260209060501.125036-1-activprithvi@gmail.com>]
[parent not found: <20260209051418.29470-1-activprithvi@gmail.com>]
[parent not found: <20260208164055.26045-1-activprithvi@gmail.com>]
[parent not found: <20260206160404.496306-1-activprithvi@gmail.com>]
[parent not found: <20260206090213.36921-1-activprithvi@gmail.com>]
* Testing for v2: configfs: add lock class key to struct configfs_fragment for frag_sem
2024-12-22 9:16 syzbot
@ 2026-01-21 15:02 Prithvi Tambewagh
2026-01-21 15:19 ` [syzbot] [fs?] possible deadlock in __configfs_open_file syzbot
-1 siblings, 1 reply; 19+ messages in thread
From: Prithvi Tambewagh @ 2026-01-21 15:02 UTC (permalink / raw)
To: syzbot+f6e8174215573a84b797
Cc: linux-fsdevel, linux-kernel, syzkaller-bugs, Prithvi Tambewagh
#syz test upstream 3a8660878839faadb4f1a6dd72c3179c1df56787
Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
fs/configfs/configfs_internal.h | 1 +
fs/configfs/dir.c | 6 +++++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/fs/configfs/configfs_internal.h b/fs/configfs/configfs_internal.h
index 0b969d0eb8ff..15bcde6c878b 100644
--- a/fs/configfs/configfs_internal.h
+++ b/fs/configfs/configfs_internal.h
@@ -21,6 +21,7 @@
struct configfs_fragment {
atomic_t frag_count;
struct rw_semaphore frag_sem;
+ struct lock_class_key frag_sem_key;
bool frag_dead;
};
diff --git a/fs/configfs/dir.c b/fs/configfs/dir.c
index 81f4f06bc87e..10c76cef88c9 100644
--- a/fs/configfs/dir.c
+++ b/fs/configfs/dir.c
@@ -163,6 +163,8 @@ static struct configfs_fragment *new_fragment(void)
if (p) {
atomic_set(&p->frag_count, 1);
init_rwsem(&p->frag_sem);
+ lockdep_register_key(&p->frag_sem_key);
+ lockdep_set_class(&p->frag_sem, &p->frag_sem_key);
p->frag_dead = false;
}
return p;
@@ -170,8 +172,10 @@ static struct configfs_fragment *new_fragment(void)
void put_fragment(struct configfs_fragment *frag)
{
- if (frag && atomic_dec_and_test(&frag->frag_count))
+ if (frag && atomic_dec_and_test(&frag->frag_count)) {
+ lockdep_unregister_key(&frag->frag_sem_key);
kfree(frag);
+ }
}
struct configfs_fragment *get_fragment(struct configfs_fragment *frag)
base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
--
2.34.1
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [syzbot] [fs?] possible deadlock in __configfs_open_file
2026-01-21 15:02 Testing for v2: configfs: add lock class key to struct configfs_fragment for frag_sem Prithvi Tambewagh
@ 2026-01-21 15:19 ` syzbot
0 siblings, 0 replies; 19+ messages in thread
From: syzbot @ 2026-01-21 15:19 UTC (permalink / raw)
To: activprithvi, linux-fsdevel, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
possible deadlock in __configfs_open_file
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/6433 is trying to acquire lock:
ffff888027868d78 (&p->frag_sem_key){.+.+}-{4:4}, at: __configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
but task is already holding lock:
ffff888027868d78 (&p->frag_sem_key){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff888027868d78 (&p->frag_sem_key){.+.+}-{4:4}, at: configfs_write_iter+0x219/0x4e0 fs/configfs/file.c:229
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&p->frag_sem_key);
lock(&p->frag_sem_key);
*** DEADLOCK ***
May be due to missing lock nesting notation
5 locks held by syz.0.17/6433:
#0: ffff888063464478 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2a2/0x370 fs/file.c:1232
#1: ffff88801efbc420 (sb_writers#12){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:738
#2: ffff8880760ba888 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x75/0x4e0 fs/configfs/file.c:226
#3: ffff888027868d78 (&p->frag_sem_key){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
#3: ffff888027868d78 (&p->frag_sem_key){.+.+}-{4:4}, at: configfs_write_iter+0x219/0x4e0 fs/configfs/file.c:229
#4: ffffffff8f409828 (target_devices_lock){+.+.}-{4:4}, at: target_core_item_dbroot_store+0x21/0x350 drivers/target/target_core_configfs.c:114
stack backtrace:
CPU: 0 UID: 0 PID: 6433 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/13/2026
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
print_deadlock_bug+0x1e9/0x240 kernel/locking/lockdep.c:3041
check_deadlock kernel/locking/lockdep.c:3093 [inline]
validate_chain kernel/locking/lockdep.c:3895 [inline]
__lock_acquire+0x1106/0x1c90 kernel/locking/lockdep.c:5237
lock_acquire kernel/locking/lockdep.c:5868 [inline]
lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
down_read+0x9b/0x480 kernel/locking/rwsem.c:1537
__configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
do_dentry_open+0x982/0x1530 fs/open.c:965
vfs_open+0x82/0x3f0 fs/open.c:1097
do_open fs/namei.c:3975 [inline]
path_openat+0x1de4/0x2cb0 fs/namei.c:4134
do_filp_open+0x20b/0x470 fs/namei.c:4161
file_open_name+0x2a3/0x450 fs/open.c:1381
filp_open+0x4b/0x80 fs/open.c:1401
target_core_item_dbroot_store+0x108/0x350 drivers/target/target_core_configfs.c:134
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x306/0x4e0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x7d3/0x11d0 fs/read_write.c:686
ksys_write+0x12a/0x250 fs/read_write.c:738
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd76878eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd7696dd038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fd7689e5fa0 RCX: 00007fd76878eec9
RDX: 0000000000000fff RSI: 0000200000000000 RDI: 0000000000000003
RBP: 00007fd768811f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd7689e6038 R14: 00007fd7689e5fa0 R15: 00007ffe6bade968
</TASK>
db_root: not a directory: /sys/kernel/config/target/dbroot
Tested on:
commit: 3a866087 Linux 6.18-rc1
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14c307fc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e854293d7f44b5a5
dashboard link: https://syzkaller.appspot.com/bug?extid=f6e8174215573a84b797
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17d7979a580000
^ permalink raw reply [flat|nested] 19+ messages in thread
* Syzbot test for fixing recursive locking in __configfs_open_file
2024-12-22 9:16 syzbot
@ 2026-01-08 17:32 Prithvi Tambewagh
2026-01-08 17:58 ` [syzbot] [fs?] possible deadlock " syzbot
-1 siblings, 1 reply; 19+ messages in thread
From: Prithvi Tambewagh @ 2026-01-08 17:32 UTC (permalink / raw)
To: syzbot+f6e8174215573a84b797, hch, jlbec
Cc: linux-fsdevel, linux-kernel, syzkaller-bugs, Prithvi Tambewagh
#syz test upstream 3a8660878839faadb4f1a6dd72c3179c1df56787
Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
drivers/target/target_core_configfs.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/target/target_core_configfs.c b/drivers/target/target_core_configfs.c
index b19acd662726..f29052e6a87d 100644
--- a/drivers/target/target_core_configfs.c
+++ b/drivers/target/target_core_configfs.c
@@ -108,8 +108,8 @@ static ssize_t target_core_item_dbroot_store(struct config_item *item,
const char *page, size_t count)
{
ssize_t read_bytes;
- struct file *fp;
ssize_t r = -EINVAL;
+ struct path path = {};
mutex_lock(&target_devices_lock);
if (target_devices) {
@@ -131,17 +131,18 @@ static ssize_t target_core_item_dbroot_store(struct config_item *item,
db_root_stage[read_bytes - 1] = '\0';
/* validate new db root before accepting it */
- fp = filp_open(db_root_stage, O_RDONLY, 0);
- if (IS_ERR(fp)) {
+ r = kern_path(db_root_stage, LOOKUP_FOLLOW, &path);
+ if (r) {
pr_err("db_root: cannot open: %s\n", db_root_stage);
goto unlock;
}
- if (!S_ISDIR(file_inode(fp)->i_mode)) {
- filp_close(fp, NULL);
+ if (!d_is_dir(path.dentry)) {
+ path_put(&path);
pr_err("db_root: not a directory: %s\n", db_root_stage);
+ r = -ENOTDIR;
goto unlock;
}
- filp_close(fp, NULL);
+ path_put(&path);
strscpy(db_root, db_root_stage);
pr_debug("Target_Core_ConfigFS: db_root set to %s\n", db_root);
base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
--
2.34.1
^ permalink raw reply related [flat|nested] 19+ messages in thread* [syzbot] [fs?] possible deadlock in __configfs_open_file
@ 2024-12-22 9:16 syzbot
0 siblings, 0 replies; 19+ messages in thread
From: syzbot @ 2024-12-22 9:16 UTC (permalink / raw)
To: hch, jlbec, linux-fsdevel, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: eabcdba3ad40 Merge tag 'for-6.13-rc3-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17791f44580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769
dashboard link: https://syzkaller.appspot.com/bug?extid=f6e8174215573a84b797
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=1449ccf8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a37730580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9904ed2be77/disk-eabcdba3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb8d571e1cb3/vmlinux-eabcdba3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/76349070db25/bzImage-eabcdba3.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f6e8174215573a84b797@syzkaller.appspotmail.com
============================================
WARNING: possible recursive locking detected
6.13.0-rc3-syzkaller-00073-geabcdba3ad40 #0 Not tainted
--------------------------------------------
syz-executor381/5829 is trying to acquire lock:
ffff8880268ded78 (&p->frag_sem){.+.+}-{4:4}, at: __configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
but task is already holding lock:
ffff8880268ded78 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff8880268ded78 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x216/0x4b0 fs/configfs/file.c:229
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&p->frag_sem);
lock(&p->frag_sem);
*** DEADLOCK ***
May be due to missing lock nesting notation
4 locks held by syz-executor381/5829:
#0: ffff88801e7f0420 (sb_writers#9){.+.+}-{0:0}, at: ksys_write+0x12b/0x250 fs/read_write.c:731
#1: ffff888026d52688 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x75/0x4b0 fs/configfs/file.c:226
#2: ffff8880268ded78 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
#2: ffff8880268ded78 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x216/0x4b0 fs/configfs/file.c:229
#3: ffffffff8ee089c8 (target_devices_lock){+.+.}-{4:4}, at: target_core_item_dbroot_store+0x23/0x2e0 drivers/target/target_core_configfs.c:114
stack backtrace:
CPU: 1 UID: 0 PID: 5829 Comm: syz-executor381 Not tainted 6.13.0-rc3-syzkaller-00073-geabcdba3ad40 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
print_deadlock_bug+0x2e3/0x410 kernel/locking/lockdep.c:3037
check_deadlock kernel/locking/lockdep.c:3089 [inline]
validate_chain kernel/locking/lockdep.c:3891 [inline]
__lock_acquire+0x2117/0x3c40 kernel/locking/lockdep.c:5226
lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849
down_read+0x9a/0x330 kernel/locking/rwsem.c:1524
__configfs_open_file+0xe8/0x9c0 fs/configfs/file.c:304
do_dentry_open+0xf59/0x1ea0 fs/open.c:945
vfs_open+0x82/0x3f0 fs/open.c:1075
do_open fs/namei.c:3828 [inline]
path_openat+0x1e6a/0x2d60 fs/namei.c:3987
do_filp_open+0x20c/0x470 fs/namei.c:4014
file_open_name+0x2a4/0x450 fs/open.c:1347
filp_open+0x4b/0x80 fs/open.c:1367
target_core_item_dbroot_store+0x10d/0x2e0 drivers/target/target_core_configfs.c:134
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x2f6/0x4b0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:586 [inline]
vfs_write+0x5ae/0x1150 fs/read_write.c:679
ksys_write+0x12b/0x250 fs/read_write.c:731
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f70a1169979
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcb84c8f08 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f70a11b3300 RCX: 00007f70a1169979
RDX: 0000000000000080 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 00007f70a11b30fd R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000006 R11: 0000000000000246 R12: 00007f70a11b817c
---
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
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2026-02-16 5:42 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20260207104321.156237-1-activprithvi@gmail.com>
2026-02-07 10:55 ` [syzbot] [fs?] possible deadlock in __configfs_open_file syzbot
[not found] <20260216051808.39072-1-activprithvi@gmail.com>
2026-02-16 5:42 ` syzbot
[not found] <20260216042729.31754-1-activprithvi@gmail.com>
2026-02-16 4:29 ` syzbot
[not found] <20260210140002.27253-1-activprithvi@gmail.com>
2026-02-10 14:24 ` syzbot
[not found] <20260210135257.23957-1-activprithvi@gmail.com>
2026-02-10 13:54 ` syzbot
[not found] <20260210134807.21522-1-activprithvi@gmail.com>
2026-02-10 13:50 ` syzbot
[not found] <20260210134120.18174-1-activprithvi@gmail.com>
2026-02-10 13:43 ` syzbot
[not found] <20260209154456.48661-1-activprithvi@gmail.com>
2026-02-09 16:09 ` syzbot
[not found] <20260209153733.45193-1-activprithvi@gmail.com>
2026-02-09 15:39 ` syzbot
[not found] <20260209150120.31598-1-activprithvi@gmail.com>
2026-02-09 15:26 ` syzbot
[not found] <20260209142936.18000-1-activprithvi@gmail.com>
2026-02-09 14:46 ` syzbot
[not found] <20260209060501.125036-1-activprithvi@gmail.com>
2026-02-09 6:06 ` syzbot
[not found] <20260209051418.29470-1-activprithvi@gmail.com>
2026-02-09 5:16 ` syzbot
[not found] <20260208164055.26045-1-activprithvi@gmail.com>
2026-02-08 16:42 ` syzbot
[not found] <20260206160404.496306-1-activprithvi@gmail.com>
2026-02-06 16:05 ` syzbot
[not found] <20260206090213.36921-1-activprithvi@gmail.com>
2026-02-06 9:04 ` syzbot
2026-01-21 15:02 Testing for v2: configfs: add lock class key to struct configfs_fragment for frag_sem Prithvi Tambewagh
2026-01-21 15:19 ` [syzbot] [fs?] possible deadlock in __configfs_open_file syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-01-08 17:32 Syzbot test for fixing recursive locking " Prithvi Tambewagh
2026-01-08 17:58 ` [syzbot] [fs?] possible deadlock " syzbot
2024-12-22 9:16 syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox