From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <andreas.dilger@oracle.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Alessandro Polverini <alex@nibbles.it>,
Christoph Biedl <bugzilla.kernel.bpeb@manchmal.in-ulm.de>
Subject: Re: [PATCH] resize: check s_log_groups_per_flex before accessing flex groups
Date: Sun, 28 Mar 2010 10:26:50 -0500 [thread overview]
Message-ID: <4BAF753A.3070704@redhat.com> (raw)
In-Reply-To: <96C33B08-CDC5-48B3-98C0-479F230E7F98@oracle.com>
Andreas Dilger wrote:
> On 2010-03-27, at 13:32, Eric Sandeen wrote:
>> #13549, Kernel oops while online resizing of an ext4 filesystem
>>
>> if groups_per_flex < 2, sbi->s_flex_groups[] doesn't get filled out,
>> and every other access to this first tests s_log_groups_per_flex;
>> same thing needs to happen in resize or we'll wander off into
>> a null pointer.
>
> Does it even make sense to set INCOMPAT_FLEX_BG if we only have a single
> group per flexbg? That is just a normal filesystem then. That would be
> a separate bug in mke2fs.
yes, I really wondered about that, but we have this check throughout the
ext4 kernel code right now, so as a quick fix ...
(note in this case it was an ext3 fs converted to ext4, with tune2fs:)
# tune2fs -O extents,uninit_bg,dir_index,flex_bg,huge_file,dir_nlink,extra_isize fsfile
I haven't honestly looked at what it means to "turn on" flex_bg
for a filesystem not originally mkfs'd with it. I'm not sure it does
anything other than setting the flag, leaving flex group size == group size.
Thanks,
-Eric
next prev parent reply other threads:[~2010-03-28 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 19:32 [PATCH] resize: check s_log_groups_per_flex before accessing flex groups Eric Sandeen
2010-03-28 15:14 ` Andreas Dilger
2010-03-28 15:26 ` Eric Sandeen [this message]
2010-04-04 2:11 ` tytso
2010-04-04 2:17 ` tytso
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=4BAF753A.3070704@redhat.com \
--to=sandeen@redhat.com \
--cc=alex@nibbles.it \
--cc=andreas.dilger@oracle.com \
--cc=bugzilla.kernel.bpeb@manchmal.in-ulm.de \
--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).