From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Don't print error when listing too many xattrs.
Date: Mon, 4 May 2009 10:06:24 -0700 [thread overview]
Message-ID: <20090504170624.GC31249@mail.oracle.com> (raw)
In-Reply-To: <1241385489-24389-1-git-send-email-tao.ma@oracle.com>
On Mon, May 04, 2009 at 05:18:09AM +0800, Tao Ma wrote:
> Currently, when listing xattrs, kernel define XATTR_LIST_MAX as 65536
> in include/linux/limits.h, so it can't handle too many xattrs.
>
> But with ocfs2 xattr tree, we actually have no limit for the number.
> And it will pollute the message with something like this when listing.
> (27738,0):ocfs2_iterate_xattr_buckets:3158 ERROR: status = -34
> (27738,0):ocfs2_xattr_tree_list_index_block:3264 ERROR: status = -34
>
> So don't print "ERROR" message as this is not an ocfs2 error.
Hmm, but this will stop iteration of the xattrs right where we
hit the large one. I don't think that's correct. At the very least, we
should go on listing with the following xattrs.
Now, the xattr with a too-long name - should we skip it, or
should we list a truncated name? That I'm not sure of.
Joel
--
print STDOUT q
Just another Perl hacker,
unless $spring
- Larry Wall
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-05-04 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 21:18 [Ocfs2-devel] [PATCH] ocfs2: Don't print error when listing too many xattrs Tao Ma
2009-05-04 17:06 ` Joel Becker [this message]
2009-05-05 1:40 ` Tao Ma
2009-05-05 7:18 ` Joel Becker
2009-05-05 7:39 ` Tao Ma
2009-05-05 23:11 ` Joel Becker
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=20090504170624.GC31249@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.