From: Dave Chinner <david@fromorbit.com>
To: Kasparek Tomas <kasparek@fit.vutbr.cz>
Cc: "Michael L. Semon" <mlsemon35@gmail.com>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: How to use increased number of ACL entries?
Date: Tue, 5 Nov 2013 07:46:47 +1100 [thread overview]
Message-ID: <20131104204647.GO6188@dastard> (raw)
In-Reply-To: <20131104151050.GS9974@fit.vutbr.cz>
On Mon, Nov 04, 2013 at 04:10:50PM +0100, Kasparek Tomas wrote:
> On Mon, Nov 04, 2013 at 08:24:25AM -0600, Eric Sandeen wrote:
> > > However, it should be dirent (ftype=1 in the above output) that keeps a
> > > vanilla 3.10.17 kernel from mounting the resulting filesystem:
> >
> > I'm sorry, you are right - it hit kernel v3.11:
> >
> > 5c87d4bc1a86bd6e6754ac3d6e111d776ddcfe57 xfs: increase number of ACL entries for V5 superblocks
> >
> > $ git describe --contains 5c87d4bc1a86bd6e6754ac3d6e111d776ddcfe57
> > v3.11-rc1~18^2~41
>
> And get to stable 3.10 later.
>
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=0a8aa1939777dd114479677f0044652c1fd72398
No, that never went into the 3.10 stable tree, and nor should it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-04 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 8:17 How to use increased number of ACL entries? Kasparek Tomas
2013-11-04 0:39 ` Dave Chinner
2013-11-04 2:37 ` Eric Sandeen
2013-11-04 4:18 ` Michael L. Semon
2013-11-04 4:35 ` Jeff Liu
2013-11-04 5:52 ` Michael L. Semon
2013-11-04 15:05 ` Kasparek Tomas
2013-11-04 14:24 ` Eric Sandeen
2013-11-04 15:10 ` Kasparek Tomas
2013-11-04 20:46 ` Dave Chinner [this message]
2013-11-05 22:03 ` Michael L. Semon
2013-11-05 22:46 ` Ben Myers
2013-11-04 20:53 ` Dave Chinner
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=20131104204647.GO6188@dastard \
--to=david@fromorbit.com \
--cc=kasparek@fit.vutbr.cz \
--cc=mlsemon35@gmail.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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.