From: Samuel Thibault <sthibault@debian.org>
To: 738758@bugs.debian.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Bug#738758: [PATCH] ext4: optimize Hurd tests when reading/writing inodes
Date: Fri, 21 Mar 2014 18:11:14 +0100 [thread overview]
Message-ID: <20140321171114.GA5601@type.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <1395420533-20103-1-git-send-email-tytso@mit.edu>
Theodore Ts'o, le Fri 21 Mar 2014 12:48:53 -0400, a écrit :
> Also, add a sanity check to make sure the 64-bit feature is not set
> for Hurd file systems, since i_file_acl_high conflicts with a
> Hurd-specific field. This is not a big deal, since Hurd doesn't
> support file systems larger than 1GB[1] anyway.
Err, it does. We regularly use volumes with dozens of GiB.
> [1] http://walfield.org/pub/people/neal/papers/hurd-faq/FAQ.en.html#q2-6
That faq is very largely outdated. See the official faq on
http://www.gnu.org/software/hurd/faq.html
Samuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
prev parent reply other threads:[~2014-03-21 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140212185534.GA4005@phenomenon>
2014-03-19 20:20 ` Bug#738758: linux-image-3.12-1-amd64: ext4 can't properly handle ext2 filesystems created for GNU/Hurd Gabriele Giacone
2014-03-20 4:34 ` [PATCH] ext4: kill i_version support for Hurd-castrated file systems Theodore Ts'o
2014-03-20 5:27 ` Andreas Dilger
2014-03-20 8:10 ` Christoph Hellwig
2014-03-20 14:44 ` tytso
2014-03-20 17:30 ` Bug#738758: " Ben Hutchings
2014-03-21 14:39 ` tytso
2014-03-21 16:48 ` [PATCH] ext4: optimize Hurd tests when reading/writing inodes Theodore Ts'o
2014-03-21 17:11 ` Samuel Thibault [this message]
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=20140321171114.GA5601@type.youpi.perso.aquilenet.fr \
--to=sthibault@debian.org \
--cc=738758@bugs.debian.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).