linux-ext4 - Re: j_recover_fast_commit: : failed on musl-riscv64

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAD+ocbxUz1kA_7F3f_xXS6_eVt1c0NeMoMXsBQ7z2LbmrMjgMg@mail.gmail.com>
Date:   Fri, 12 Feb 2021 08:11:02 -0800
From:   harshad shirwadkar <harshadshirwadkar@...il.com>
To:     Drew DeVault <sir@...wn.com>
Cc:     "Theodore Ts'o" <tytso@....edu>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: j_recover_fast_commit: : failed on musl-riscv64

Hi Drew,

I'd be happy to take a look at this and if you could provide shell
access, that would be great. From the logs you shared above, it looks
like e2fsck is crashing resulting in fast commit recovery being
aborted.

Thanks,
Harshad

On Fri, Feb 12, 2021 at 5:30 AM Drew DeVault <sir@...wn.com> wrote:
>
> On Thu Feb 11, 2021 at 11:03 PM EST, Theodore Ts'o wrote:
> > Can you try using glibc on RiscV and see if it passes with glibc?
>
> Hm, I don't have a glibc+RISC-V setup readily available for testing, nor
> could I obtain one easily. But I would be open to offering shell access
> in my musl environment for troubleshooting purposes - would you (or
> any other maintainers) find that helpful?