Linux FUSE: Fix exclusive lock for parallel page cache IO in FUSE_I_CACHE_IO_MODE

From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - The vulnerability is described as "fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set". - This is a vulnerability related to FUSE (Filesystem in Userspace), involving the use of an exclusive lock when FUSE_I_CACHE_IO_MODE is enabled. 2. Fix Code: - The fix is located in the file , specifically at line 1345. - The function was modified to change its return value from to . 3. Reason for Fix: - The reason for the fix is "shared locks are not allowed with parallel page cache IO". - This means that shared locks cannot be used in conjunction with parallel page cache I/O operations. 4. Fix Context: - The context of the fix explains that shared locks are not permitted when FUSE_I_CACHE_IO_MODE is set. - If shared locks are used, the wait in may hang indefinitely. 5. Fix History: - The commit message for the fix is "fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set". - The commit ID is . 6. Fix Author and Reviewers: - The author of the fix is . - The reviewers include , , and . 7. Fix Status: - The fix has been merged into the branch and has been reviewed by . With this information, we can understand the fix process, the underlying cause, and the code changes introduced by the patch.

Goal Reached Thanks to every supporter — we hit 100%!

Linux FUSE: Fix exclusive lock for parallel page cache IO in FUSE_I_CACHE_IO_MODE