From: <gregkh@linuxfoundation.org>
To: tytso@mit.edu, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "ext4: return EROFS if device is r/o and journal replay is needed" has been added to the 4.10-stable tree
Date: Wed, 08 Mar 2017 16:38:56 +0100 [thread overview]
Message-ID: <148898753641143@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
ext4: return EROFS if device is r/o and journal replay is needed
to the 4.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ext4-return-erofs-if-device-is-r-o-and-journal-replay-is-needed.patch
and it can be found in the queue-4.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 4753d8a24d4588657bc0a4cd66d4e282dff15c8c Mon Sep 17 00:00:00 2001
From: Theodore Ts'o <tytso@mit.edu>
Date: Sun, 5 Feb 2017 01:26:48 -0500
Subject: ext4: return EROFS if device is r/o and journal replay is needed
From: Theodore Ts'o <tytso@mit.edu>
commit 4753d8a24d4588657bc0a4cd66d4e282dff15c8c upstream.
If the file system requires journal recovery, and the device is
read-ony, return EROFS to the mount system call. This allows xfstests
generic/050 to pass.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/ext4/super.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -3927,7 +3927,8 @@ static int ext4_fill_super(struct super_
* root first: it may be modified in the journal!
*/
if (!test_opt(sb, NOLOAD) && ext4_has_feature_journal(sb)) {
- if (ext4_load_journal(sb, es, journal_devnum))
+ err = ext4_load_journal(sb, es, journal_devnum);
+ if (err)
goto failed_mount3a;
} else if (test_opt(sb, NOLOAD) && !(sb->s_flags & MS_RDONLY) &&
ext4_has_feature_journal_needs_recovery(sb)) {
Patches currently in stable-queue which might be from tytso@mit.edu are
queue-4.10/ext4-fix-data-corruption-in-data-journal-mode.patch
queue-4.10/ext4-fix-use-after-iput-when-fscrypt-contexts-are-inconsistent.patch
queue-4.10/ext4-return-erofs-if-device-is-r-o-and-journal-replay-is-needed.patch
queue-4.10/ext4-include-forgotten-start-block-on-fallocate-insert-range.patch
queue-4.10/ext4-preserve-the-needs_recovery-flag-when-the-journal-is-aborted.patch
queue-4.10/ext4-fix-deadlock-between-inline_data-and-ext4_expand_extra_isize_ea.patch
queue-4.10/ext4-trim-allocation-requests-to-group-size.patch
queue-4.10/ext4-do-not-polute-the-extents-cache-while-shifting-extents.patch
queue-4.10/ext4-fix-fencepost-in-s_first_meta_bg-validation.patch
queue-4.10/ext4-fix-inline-data-error-paths.patch
queue-4.10/jbd2-don-t-leak-modified-metadata-buffers-on-an-aborted-journal.patch
reply other threads:[~2017-03-08 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=148898753641143@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.