linux-kernel - Re: [PATCH v2] loop: Disable fallocate() zero and discard if not supported

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: <171836769633.229112.12813343173922846778.b4-ty@kernel.dk>
Date: Fri, 14 Jun 2024 06:21:36 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Christoph Hellwig <hch@...radead.org>, linux-block@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Cyril Hrubis <chrubis@...e.cz>
Cc: Jan Kara <jack@...e.cz>
Subject: Re: [PATCH v2] loop: Disable fallocate() zero and discard if not
 supported


On Thu, 13 Jun 2024 18:38:17 +0200, Cyril Hrubis wrote:
> If fallcate is implemented but zero and discard operations are not
> supported by the filesystem the backing file is on we continue to fill
> dmesg with errors from the blk_mq_end_request() since each time we call
> fallocate() on the loop device the EOPNOTSUPP error from lo_fallocate()
> ends up propagated into the block layer. In the end syscall succeeds
> since the blkdev_issue_zeroout() falls back to writing zeroes which
> makes the errors even more misleading and confusing.
> 
> [...]

Applied, thanks!

[1/1] loop: Disable fallocate() zero and discard if not supported
      commit: 5f75e081ab5cbfbe7aca2112a802e69576ee9778

Best regards,
-- 
Jens Axboe