From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 36172] "kernel BUG at fs/ext4/super.c" triggered after tune2fs/remount
Date: Tue, 31 May 2011 19:07:03 GMT [thread overview]
Message-ID: <201105311907.p4VJ73O4025668@demeter1.kernel.org> (raw)
In-Reply-To: <bug-36172-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=36172
Jan Kara <jack@suse.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jack@suse.cz
--- Comment #2 from Jan Kara <jack@suse.cz> 2011-05-31 19:07:00 ---
Sorry, the fix is wrong. The problem is that we set EXT4_SB(sb)->s_journal in
ext4_fill_super() but we don't change it appropriately in ext4_remount() when
journal feature could have changed. I'm actually not sure if this is even
supposed to work - whether it isn't bug in tune2fs that it allows changing of
has_journal feature on mounted filesystem. Because when tune2fs removes the
feature and possibly other journal parameters from superblock, we really have
not any guarantee that the journal is still correct. In fact the journal space
could have been already reused for something else. So fixing this would need
some careful look... Ted?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-05-31 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 19:23 [Bug 36172] New: "kernel BUG at fs/ext4/super.c" triggered after tune2fs/remount bugzilla-daemon
2011-05-29 21:50 ` [Bug 36172] " bugzilla-daemon
2011-05-31 19:07 ` bugzilla-daemon [this message]
2011-05-31 19:29 ` bugzilla-daemon
2012-08-24 12:48 ` bugzilla-daemon
2012-08-24 14:01 ` bugzilla-daemon
2012-08-24 15:36 ` bugzilla-daemon
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=201105311907.p4VJ73O4025668@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).