Michael Tokarev d096ad0f79 ext4: do not try to write superblock on ro remount w/o journal
When a journal-less ext4 filesystem is mounted on a read-only block
device (blockdev --setro will do), each remount (for other, unrelated,
flags, like suid=>nosuid etc) results in a series of scary messages
from kernel telling about I/O errors on the device.

This is becauese of the following code ext4_remount():

       if (sbi->s_journal == NULL)
                ext4_commit_super(sb, 1);

at the end of remount procedure, which forces writing (flushing) of
a superblock regardless whenever it is dirty or not, if the filesystem
is readonly or not, and whenever the device itself is readonly or not.

We only need call ext4_commit_super when the file system had been
previously mounted read/write.

Thanks to Eric Sandeen for help in diagnosing this issue.

Signed-off-By: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@vger.kernel.org
2012-12-25 14:08:16 -05:00
..
2012-07-14 16:38:34 +04:00
2012-10-09 23:33:38 -04:00
2012-10-09 16:22:17 +09:00
2012-10-09 23:33:38 -04:00
2012-10-09 15:04:25 +01:00
2012-10-17 09:18:38 -05:00
2012-10-09 18:35:22 -04:00
2012-10-09 16:22:17 +09:00
2012-10-09 16:22:17 +09:00
2012-10-06 03:05:31 +09:00
2012-07-14 16:34:47 +04:00
2012-10-09 23:33:39 -04:00
2012-10-09 16:22:17 +09:00
2012-10-09 23:33:39 -04:00
2012-09-07 14:57:46 -04:00
2012-07-14 16:34:47 +04:00
2012-10-22 08:50:37 +03:00
2012-10-16 13:36:50 -04:00
2012-10-09 15:52:31 +09:00
2012-07-14 16:32:47 +04:00
2012-12-10 16:30:43 -05:00
2012-10-09 18:35:22 -04:00
2012-07-14 16:32:48 +04:00
2012-09-26 21:08:52 -04:00
2012-10-09 23:33:39 -04:00