Re: inconsistent lock state in io_uring_add_task_file
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: syzbot <syzbot+27c12725d8ff0bfe1a13@xxxxxxxxxxxxxxxxxxxxxxxxx>, io-uring@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx
Subject
: Re: inconsistent lock state in io_uring_add_task_file
From
: Jens Axboe <axboe@xxxxxxxxx>
Date
: Fri, 9 Oct 2020 09:06:00 -0600
In-reply-to
: <
000000000000358ba805b1385785@google.com
>
User-agent
: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
#syz fix: io_uring: no need to call xa_destroy() on empty xarray -- Jens Axboe
References
:
inconsistent lock state in io_uring_add_task_file
From:
syzbot
Prev by Date:
Re: [PATCH 2/3] io_uring: Fix XArray usage in io_uring_add_task_file
Next by Date:
RE: [PATCH v5 08/10] fs/ntfs3: Add Kconfig, Makefile and doc
Previous by thread:
inconsistent lock state in io_uring_add_task_file
Next by thread:
KASAN: use-after-free Read in __io_uring_files_cancel
Index(es):
Date
Thread
[Index of Archives]
[Linux Ext4 Filesystem]
[Union Filesystem]
[Filesystem Testing]
[Ceph Users]
[Ecryptfs]
[AutoFS]
[Kernel Newbies]
[Share Photos]
[Security]
[Netfilter]
[Bugtraq]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux Cachefs]
[Reiser Filesystem]
[Linux RAID]
[Samba]
[Device Mapper]
[CEPH Development]