linux-ext4 - Re: [PATCH 06/13] ext4: Drop special handling of journalled data from ext4_sync

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]

Date:   Wed, 29 Mar 2023 17:05:45 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Jan Kara <jack@...e.cz>
Cc:     Ted Tso <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 06/13] ext4: Drop special handling of journalled data
 from ext4_sync_file()

On Wed, Mar 29, 2023 at 05:49:37PM +0200, Jan Kara wrote:
>  	/*
> -	 * data=writeback,ordered:
>  	 *  The caller's filemap_fdatawrite()/wait will sync the data.
>  	 *  Metadata is in the journal, we wait for proper transaction to
>  	 *  commit here.

Nit: without the list, the two space indent looks a bit weird here.

>  	if (!sbi->s_journal)
>  		ret = ext4_fsync_nojournal(inode, datasync, &needs_barrier);
> -	else if (ext4_should_journal_data(inode))
> -		ret = ext4_force_commit(inode->i_sb);
>  	else
>  		ret = ext4_fsync_journal(inode, datasync, &needs_barrier);

Also if there is not journale the above comment doesn't make much sense.
But I'm really not sure the comment adds any value to start with, so
maybe just drop it entirely?