linux-ext4 - Re: [BUG] Tune2fs and fuse2fs do not change j_tail

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 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:   Thu, 4 Aug 2022 16:30:40 +0800
From:   zhanchengbin <zhanchengbin1@...wei.com>
To:     Alexey Lyahkov <alexey.lyashkov@...il.com>
CC:     Theodore Ts'o <tytso@....edu>, <linux-ext4@...r.kernel.org>,
        linfeilong <linfeilong@...wei.com>, <liuzhiqiang26@...wei.com>,
        <liangyun2@...wei.com>
Subject: Re: [BUG] Tune2fs and fuse2fs do not change j_tail_sequence in
 journal superblock

> Hi
> 
> Thanks for you report.
> Problem much bigger than it. Debugs based code lack many parts of journal handling, including fast commit.
> Journal tag v3, and other.

I think we can solve the current problem first.

> 
> Alex
> 
>> On 2 Aug 2022, at 14:23, zhanchengbin <zhanchengbin1@...wei.com> wrote:

<snip>

>> There are two existing solutions:
>> 1) Add "journal->j_tail_sequence = journal->j_transaction_sequence" in to the
>> recover_ext3_journal in debugfs/journal.c.

I want to use the first solution, do you have any other solutions?

Thanks.

>> 2) There is a timestamp in the commit block, so we can add timestamp check when
>> the log is replayed.
> 
> .
>