[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160804161814.GB12861@quack2.suse.cz>
Date: Thu, 4 Aug 2016 18:18:14 +0200
From: Jan Kara <jack@...e.cz>
To: Theodore Ts'o <tytso@....edu>
Cc: Jan Kara <jack@...e.cz>, Dave Chinner <david@...morbit.com>,
Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: [4.7-rc6 ext3 BUG] kernel BUG at fs/ext4/xattr.c:1331
On Mon 01-08-16 09:09:05, Ted Tso wrote:
> On Mon, Aug 01, 2016 at 02:19:30PM +0200, Jan Kara wrote:
> > Regarding your patch - I think it's a reasonable band-aid although I'll
> > have to backport proper fixes to 4.4 anyway (it's a base of our next
> > enterprise release), which is where i_projid got introduced as well, so
> > eventually we will have proper stable fixes for all relevant kernels
> > anyway.
>
> Well, it depends on whether you intend to support upgrading an
> existing file system or require users to run mkfs.ext4 before being
> able to take advantage of the new feature. Red Hat is much more
> conservative and has historically only supported running mke2fs from
> scratch --- which probably made sense from their QA department's POV,
> anyway. The band-aid patch is enough if you don't suppor "tune2fs -O
> project", but only "mke2fs -t ext4 -O project". I'd personally prefer
> upstream to support both flawlesssly, so I'm thankful for your work to
> fix things properly, but enterprise distros can be extremely
> conservative.
Well, in SUSE we were initially very conservative about ext4 but as ext4
has matured, we are not that cautious anymore. So e.g. turning on project
quota feature would be something we'd like to support unless there is a
really good reason not to...
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
--
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
Powered by blists - more mailing lists