lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJfpegsnLAAnpxw+sJ9tcf5dLfcyK3mX0Jg7+XuM2Yk7Dfk8kw@mail.gmail.com>
Date: Tue, 27 Jan 2026 10:57:59 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Zhang Tianci <zhangtianci.1997@...edance.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	xieyongji@...edance.com, Li Yichao <liyichao.1@...edance.com>
Subject: Re: [PATCH] fuse: set ff->flock only on success

On Thu, 25 Dec 2025 at 12:12, Zhang Tianci
<zhangtianci.1997@...edance.com> wrote:
>
> If FUSE_SETLK fails (e.g., due to EWOULDBLOCK), we shall not set
> FUSE_RELEASE_FLOCK_UNLOCK in fuse_file_release().

It's not clear if this is an optimization, a correctness fix or neither?

Thanks,
Miklos

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ