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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 14 May 2019 11:20:54 +0200
From:   Heiko Carstens <heiko.carstens@...ibm.com>
To:     Jan Stancek <jstancek@...hat.com>, "Theodore Ts'o" <tytso@....edu>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        lkft-triage@...ts.linaro.org, ltp@...ts.linux.it,
        LKML <linux-kernel@...r.kernel.org>, linux-ext4@...r.kernel.org,
        Arthur Marsh <arthur.marsh@...ernode.on.net>,
        Richard Weinberger <richard.weinberger@...il.com>
Subject: Re: [LTP] LTP: Syscalls: 274 failures: EROFS(30): Read-only file
 system

On Mon, May 13, 2019 at 03:16:11AM -0400, Jan Stancek wrote:
> ----- Original Message -----
> > We have noticed 274 syscall test failures on x86_64 and i386 due to
> > Make the temporary directory in one shot using mkdtemp failed.
> > tst_tmpdir.c:264: BROK: tst_tmpdir:
> > mkdtemp(/scratch/ltp-7D8vAcYeFG/OXuquJ) failed: EROFS
> 
> Looks like ext4 bug:
> 
> [ 1916.032087] EXT4-fs error (device sda): ext4_find_extent:909: inode #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0)
> [ 1916.073840] jbd2_journal_bmap: journal block not found at offset 4455 on sda-8
> [ 1916.081071] Aborting journal on device sda-8.
> [ 1916.348652] EXT4-fs error (device sda): ext4_journal_check_start:61: Detected aborted journal
> [ 1916.357222] EXT4-fs (sda): Remounting filesystem read-only
> 
> So best place for report is likely linux-ext4@...r.kernel.org

Actually adding the mailing list, since there has been at least one
other report about ext4 filesystem corruption.

FWIW, I've seen the above also at least once on s390 when using a
kernel built with git commit 47782361aca2.

> > 
> > Failed log:
> > ------------
> > pread01     1  TBROK  :  tst_tmpdir.c:264: tst_tmpdir:
> > mkdtemp(/scratch/ltp-7D8vAcYeFG/preAUvXAE) failed: errno=EROFS(30):
> > Read-only file system
> > pread01     2  TBROK  :  tst_tmpdir.c:264: Remaining cases broken
> > 
> > full test log,
> > --------------
> > https://lkft.validation.linaro.org/scheduler/job/711826#L7834
> > 
> > LTP Version: 20190115
> > 
> > Kernel bad commit:
> > ------------
> > git branch master
> > git commit dd5001e21a991b731d659857cd07acc7a13e6789
> > git describe v5.1-3486-gdd5001e21a99
> > git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > 
> > Kernel good commit:
> > ------------
> > git branch master
> > git commit d3511f53bb2475f2a4e8460bee5a1ae6dea2a433
> > git describe v5.1-3385-gd3511f53bb24
> > git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > 
> > Best regards
> > Naresh Kamboju
> > 
> 
> -- 
> Mailing list info: https://lists.linux.it/listinfo/ltp

Powered by blists - more mailing lists