linux-ext4 - e2fsprogs: Fsck of read-only FS w/ external journal fails after 1.42.5?

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-next>] [day] [month] [year] [list]

Message-ID: <20130504195350.GA20046@gmail.com>
Date:	Sat, 4 May 2013 14:53:50 -0500
From:	Calvin Owens <jcalvinowens@...il.com>
To:	Theodore Ts'o <tytso@....edu>, Eric Sandeen <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: e2fsprogs: Fsck of read-only FS w/ external journal fails after
 1.42.5?

Hello all,

Commit a85f8350 (http://goo.gl/aCykm) makes it impossible to fsck an
ext4 filesystem w/ external journal if it is mounted read-only. Certain
distros (Gentoo in my case) expect to be able to do this on the root
filesystem at boot time, and get very upset if they can't.

With journal checks forced now, e2fsck tries to open() the external
journal device, which always fails with -EBUSY if the filesystem is
mounted, read-only or otherwise. Is this the expected behavior? Maybe
the kernel shouldn't be returning an error there? It's been doing so
since at least v3.6.

Clearly this doesn't impact many people, since it's been in the tree for
almost a year now... but I thought I'd mention it.

Thoughts?

Thanks very much,
Calvin
--
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