linux-ext4 - [Bug 76261] ext4_da_writepages err -30 after remount ro during shutdown

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]

Message-ID: <bug-76261-13602-AQO6iw4Kin@https.bugzilla.kernel.org/>
Date:	Fri, 16 May 2014 13:44:36 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 76261] ext4_da_writepages err -30 after remount ro during
 shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=76261

--- Comment #11 from Theodore Tso <tytso@....edu> ---
Hi Ken, commit 807612db2f9940 is not going to help you, since
emergency_remount() is calling do_remount_sb with force == 0.

Note that if applications are still writing to the file system at the time of
the shutdown, the application files are at risk of getting corrupted.   It
doesn't actually really matter if sb_prepare_readonly_remount() causes those
writes to return EROFS as opposed to returning success and then having the
writes fail.  It might quiet the the error messages in the system log, but it's
not going to allow the applications to shutdown cleanly --- because if this
patch was going to make a difference, it implies that applications are not
getting shut down cleanly before android triggers the emergency_remount.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
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