linux-kernel - Re: [PATCH 00/11] Bugfix and refactoring

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: <ZiDA5uUq7a7tR78a@hovoldconsulting.com>
Date: Thu, 18 Apr 2024 08:42:46 +0200
From: Johan Hovold <johan@...nel.org>
To: Konstantin Komarov <almaz.alexandrovich@...agon-software.com>
Cc: ntfs3@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>,
	Linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 00/11] Bugfix and refactoring

On Wed, Apr 17, 2024 at 04:03:46PM +0300, Konstantin Komarov wrote:
> This series contains various fixes and refactoring for ntfs3.
> Fixed problem with incorrect link counting for files with DOS names.
>
> Konstantin Komarov (11):
>    fs/ntfs3: Remove max link count info display during driver init
>    fs/ntfs3: Missed le32_to_cpu conversion
>    fs/ntfs3: Mark volume as dirty if xattr is broken
>    fs/ntfs3: Use variable length array instead of fixed size
>    fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow
>    fs/ntfs3: Redesign ntfs_create_inode to return error code instead of
>      inode
>    fs/ntfs3: Check 'folio' pointer for NULL
>    fs/ntfs3: Always make file nonresident if fallocate (xfstest 438)
>    fs/ntfs3: Optimize to store sorted attribute definition table
>    fs/ntfs3: Remove cached label from sbi
>    fs/ntfs3: Taking DOS names into account during link counting

All the patches in this series appear to be white space damaged and
cannot be applied.

Most of the patches are lacking proper commit messages, and the bug
fixes should be clearly marked as such with a Fixes tag and CC-stable
tag where appropriate.

Also don't mix fixes with cleanups and refactoring unless the former
really depends on the latter.

At least move the independent fixes to the front of the series.

Johan