linux-ext4 - Re: [PATCH] ext4: Don't report EOPNOTSUPP errors from discard

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <170861726753.823885.4373903569687360726.b4-ty@mit.edu>
Date: Thu, 22 Feb 2024 10:54:29 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Jan Kara <jack@...e.cz>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: Don't report EOPNOTSUPP errors from discard


On Tue, 13 Feb 2024 11:16:01 +0100, Jan Kara wrote:
> When ext4 is mounted without journal, with discard mount option, and on
> a device not supporting trim, we print error for each and every freed
> extent. This is not only useless but actively harmful. Instead ignore
> the EOPNOTSUPP error. Trim is only advisory anyway and when the
> filesystem has journal we silently ignore trim error as well.
> 
> 
> [...]

Applied, thanks!

[1/1] ext4: Don't report EOPNOTSUPP errors from discard
      commit: f3edd83e2e71dd393c0f485be103a4b35f9ef41a

Best regards,
-- 
Theodore Ts'o <tytso@....edu>