linux-ext4 - Re: EXT4-fs (device loop0): panic forced after error -- bug or not?

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:	Tue, 1 Dec 2015 10:32:02 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Vegard Nossum <vegard.nossum@...cle.com>
Cc:	Andreas Dilger <adilger.kernel@...ger.ca>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: EXT4-fs (device loop0): panic forced after error -- bug or not?

On Tue, Dec 01, 2015 at 03:22:02PM +0100, Vegard Nossum wrote:
> 
> I'm a bit unsure about whether this is really a bug or not; it looks
> like the filesystem is set to panic on error but I still find it weird
> that this behaviour is allowed by default (would it still panic if
> somebody inserted this filesystem on a USB stick and it got automounted?).

If the distribution cares about this, it should automount with mount
option "errors=remount-ro".

> I call mount() with mountflags=0 and data=NULL followed by opendir() and
> readdir(), but if I just a manual mount + ls from the shell I don't see
> the panic at all, just some of the errors, so I thought maybe there's
> some sort of race somewhere?

I'm not able to reproduce this; I'm getting EACCES to the opendir().

But looking at your kernel messages, it's not a bug.

Cheers,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html