Lines Matching defs:new
144 /* Can we reuse the existing entry for the new value? */
148 /* How much space is needed for the new value? */
164 /* Fill xl_entry with a new entry */
358 u64 xb_blkno, int new)
373 if (new)
520 /* If ocfs2_read_block() got us a new bh, pass it up. */
654 * If this is a new directory with inline data,
1480 /* How much free space is needed to set the new value */
1492 * We can't leave the new entry's xe_name_offset at zero or
1571 * remove the old one and reinsert the new.
1601 * the new value, so we only need the difference. If the new
1913 * transaction and open a new one. If this is a bucket, truncate
1967 * new entry. We're not going to try and reclaim those clusters either.
1969 * the new clusters are attached safely and we can just leave the old
2002 "Unable to grow xattr %.*s safely. %u new clusters "
2052 * Take an existing entry and make it ready for the new value. This
2110 * Prepares loc->xl_entry to receive the new xattr. This includes
2996 /* Check whether the new xattr can be inserted into the inode. */
3052 * No matter whether we replace an old one or add a new one,
3121 * will be inserted into inode as a new xattr in inode.
3136 /* the new values will be stored outside. */
3161 * Now the new value will be stored inside. So if the new
3194 * new tree will be cluster based, so no meta is needed.
3206 * This cluster will be used either for new bucket or for
3207 * new xattr block.
3435 * for init security/acl xattrs of the new inode.
4171 * When the ocfs2_xattr_block is filled up, new bucket will be created
4172 * and all the xattr entries will be moved to the new bucket.
4214 /* Init new header now. */
4240 * update ocfs2_xattr_search to the new xe and base.
4490 * buckets in the last cluster of the existing extent over to the new
4495 * to insert our xattr. If the bucket move places the target in the new
4499 * first_hash will be set as the 1st xe's name_hash in the new extent.
4541 /* Find the block for the new target bucket */
4610 * Move some xattrs in old bucket(blk) to new bucket(new_blk).
4611 * first_hash will record the 1st hash of the new bucket.
4616 * value, the new bucket will be initialized as an empty one and the
4689 * initialized a new empty bucket here.
4704 /* copy the whole bucket to the new first. */
4707 /* update the new bucket. */
4724 * Now begin the modification to the new bucket.
4726 * In the new bucket, We just move the xattr entry to the beginning
4744 /* Calculate xh_free_start for the new bucket. */
4754 /* set xh->xh_num_buckets for the new xh. */
4762 /* store the first_hash of the new bucket. */
4768 * just added a new empty bucket, there is no need to modify
4833 * ACCESS_CREATE vs ACCESS_WRITE make? Well, if we allocated a new
4835 * ocfs2_mv_xattr_buckets(), and it is really new -
4839 * ocfs2_add_new_xattr_cluster() may have created a new extent
4841 * the old extent back to create space for new xattrs. That's
4842 * how we get here, and the bucket isn't really new.
4864 * extent. We copy the buckets from the cluster at last_blk to the new
4866 * we start copying. The new extent's xh_num_buckets gets set to the
4892 /* The first bucket of the new extent */
4908 * the buckets going to the new extent.
4936 * Get the new bucket ready before we dirty anything
4969 * Move some xattrs in this cluster to the new cluster.
4996 * Move some xattrs from the old cluster to the new one since they are not
4999 * new_blk starts a new separate cluster, and we will move some xattrs from
5001 * new cluster so that it can be used as e_cpos during tree insertion and
5006 * The problem is how much xattr should we move to the new one and when should
5009 * than 1 bucket, so just move half nums of bucket into the new cluster and
5011 * to the new cluster.
5015 * new one. This time, we don't need to upate the first_bh and header_bh
5016 * since they will not be moved into the new cluster.
5018 * the new one. And we set the extend flag to zero if the insert place is
5019 * moved into the new allocated cluster since no extend is needed.
5074 * Add a new cluster for xattr storage.
5076 * If the new cluster is contiguous with the previous one, it will be
5078 * If not, we will insert a new extent for it and move some xattrs in
5079 * the last cluster into the new allocated one.
5086 * indicates the bucket we will insert the new xattrs. They will be updated
5087 * when the header_bh is moved into the new cluster.
5139 * adding this new cluster, we don't surpass the limit of
5215 * new bucket, and the first bucket (3 * blk_per_bucket).
5251 * Add new xattr bucket in an extent record and adjust the buckets
5258 * If current cluster is full, we'll allocate a new one. This may not
5309 * to the new extent.
5343 * bucket is indicated by header_bh and len is the new length.
5346 * Copy the new updated xe and xe_value_root to new_xe and new_xv if needed.
5604 * add a new bucket for the insert.
5638 /* Ok, we have a new bucket, let's try again */
5743 * 2. CoW the xattr if we are setting the new value and the value
5850 * If we are deleting the xattr or the new size will be stored inside,
6177 * old_bh and new_bh are inode bh for the old and new inode.
6301 * will be moved to the new block, and a new block can only provide
6302 * half number of recs. So we multiple new blocks by 2.
6330 * be reflinked or not. If not, remove it from the new xattr header.
6395 * recs have already be copied to the new xh with the
6605 /* One more credits in case we need to add xattr flags in new inode. */
6672 * We have to handle the case that both old bucket and new bucket
6770 * will be moved to the new block, and a new block can only provide
6771 * half number of recs. So we multiple new blocks by 2.
6869 * our xattr tree we also set the xh_num_bucket for the new
6987 * Create the same xattr extent record in the new inode's xattr tree.