linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Björn JACKE" <bj@sernet.de>
Cc: Dave Chinner <david@fromorbit.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>
Subject: Re: size limit of extended attributes
Date: Tue, 5 May 2015 17:43:48 +0200	[thread overview]
Message-ID: <20150505154348.GA16223@quack.suse.cz> (raw)
In-Reply-To: <E1Ypd3w-004tWN-1a@intern.SerNet.DE>

On Tue 05-05-15 15:38:11, Björn JACKE wrote:
> On 2015-05-02 at 01:43 +1000 Dave Chinner sent off:
> > On Thu, Apr 30, 2015 at 03:57:37PM +0200, Björn JACKE wrote:
> > > Can we get rid of the 64k size limit for EAs? The API on AIX is the same as on
> > > Linux.  But there is a huge size limit - which would help us already a lot.
> > 
> > No - the maximum xattr size of 64k is encoded into the on-disk
> > format of many filesystems and that's not a simple thing to change.
> 
> I know ext4 even has a much lower limit. But some filesystems don't have a
> limit, and there the kernel 64k limit strikes in. The EA size limit of some
> file systems could also be increased. As there is a real use case for that I
> guess filesystems would like to be able to support larger EA sizes.
  Yeah, so XFS could support more than 64K in principle if I look correct.
Supporting it for ext4 would mean ondisk format change - doable but
requires some non-trivial effort.

Regarding the API, the issue with larger xattr size is that currently we
copy whole xattr into kernel memory and process it in one go. Currently
that's OK but if you want xattrs that have megabytes, it may become an
effective way to DOS a system. So to support that we'd need to change at
least the API from VFS into filesystems so that xattrs could be processed
in smaller chunks. Again doable but quite some work.

All in all I don't think this is going to happen unless someone interested
in this invests significant amount of time to make this happen.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-05 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 11:33 size limit of extended attributes Björn JACKE
2015-04-30 12:38 ` Trond Myklebust
2015-04-30 13:57   ` Björn JACKE
2015-04-30 14:35     ` Theodore Ts'o
2015-04-30 14:46     ` Boaz Harrosh
2015-04-30 16:06       ` Björn JACKE
2015-04-30 16:56         ` Boaz Harrosh
2015-05-05 13:34           ` Björn JACKE
2015-05-01 15:43     ` Dave Chinner
2015-05-05 13:38       ` Björn JACKE
2015-05-05 15:43         ` Jan Kara [this message]
2015-05-06  1:31           ` 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=20150505154348.GA16223@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=bj@sernet.de \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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 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).