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] [day] [month] [year] [list]
Message-ID: <5e91727cab412e4d15c6ebb7a3c43b5e@egervary.hu>
Date:   Wed, 12 Sep 2018 20:05:21 +0200
From:   Egerváry Gergely <gergely@...rvary.hu>
To:     linux-kernel@...r.kernel.org
Subject: Re: loop device: print_req_error - blk_update_request I/O error

Answering to myself:
It looks like ext4 lazy init does not play well with loop device.

If the ext4 filesystem was previously created with lazy init there are
I/O errors. Disabling lazy init fixes problem. Bug or feature?

Thanks,

> I'm mounting an ext4 filesystem residing on an AHCI SATA disk via loop:
>   losetup -o 64424509440 --sizelimit 34359738368 /dev/loop0 /dev/sda
>   mount -t ext4 /dev/loop0 /mnt
> 
> Works perfectly on <= 4.4.155 (latest version on 4.4.x longterm branch)
> 
> On 4.9.126 (longterm branch) I get these errors:
>   blk_update_request: I/O error, /dev/loop0, sector 23778144

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ