From: Tiger Yang <tiger.yang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data
Date: Wed, 04 Mar 2009 11:18:19 +0800 [thread overview]
Message-ID: <49ADF2FB.6060503@oracle.com> (raw)
Mark and Joel,
I found two serious bugs about xattr and inline-data.
the first bug:
in ocfs2_mknod(), we check and found the ACL or security xattr entry
could be set into inode in ocfs2_calc_xattr_init(), then don't reserve
block for them. But in ocfs2_mknod_locked(), if we found ocfs2 support
inline-data, then set id_count with the max_inline_data. After that, we
set acl/security xattr entry in ocfs2_init_acl() or
ocfs2_init_security_set(), but in there we found inode is full, then
panic at ocfs2_claim_metadata in ocfs2_xattr_block_set.
the second bug:
we don't check inline xattr in ocfs2_try_to_write_inline_data(), so the
inline data may overwrite the xattr entries which have already in inode.
thanks,
tiger
next reply other threads:[~2009-03-04 3:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 3:18 Tiger Yang [this message]
2009-03-04 3:21 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: reserve xattr block for directory inode in mknod Tiger Yang
2009-03-05 1:37 ` Joel Becker
2009-03-04 3:21 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: fix check condition of max inline data Tiger Yang
2009-03-04 3:43 ` Tao Ma
2009-03-04 5:47 ` Tiger Yang
2009-03-04 5:49 ` Tao Ma
2009-03-05 1:44 ` Joel Becker
2009-03-05 2:36 ` [Ocfs2-devel] [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data Joel Becker
2009-03-09 4:17 ` tristan.ye
2009-03-09 4:57 ` Tao Ma
2009-03-09 5:04 ` tristan.ye
2009-03-09 5:42 ` Tao Ma
2009-03-09 6:14 ` tristan.ye
2009-03-09 6:35 ` Tiger Yang
2009-03-09 6:47 ` Joel Becker
2009-03-09 6:54 ` tristan.ye
2009-03-09 7:02 ` Tao Ma
2009-03-09 7:24 ` Tiger Yang
2009-03-09 10:36 ` Tiger Yang
2009-03-09 10:39 ` Wengang Wang
2009-03-09 10:48 ` Tao Ma
2009-03-09 10:57 ` tristan.ye
2009-03-09 6:28 ` tristan.ye
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=49ADF2FB.6060503@oracle.com \
--to=tiger.yang@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.