[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEH94LimS8mUCFwmnVi876mG9GB7DWsqG9p1O=R41XJ3-u1NQg@mail.gmail.com>
Date: Sat, 14 Dec 2013 01:36:47 +0800
From: Zhi Yong Wu <zwu.kernel@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: xfstests <xfs@....sgi.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>,
linux-kernel mlist <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5/5] xfs: allow linkat() on O_TMPFILE files
On Sat, Dec 14, 2013 at 12:41 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Fri, Dec 13, 2013 at 10:27:53PM +0800, Zhi Yong Wu wrote:
>> From: Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
>>
>> Enable O_TMPFILE support in linkat().
>> For more info, please refer to:
>> http://oss.sgi.com/archives/xfs/2013-08/msg00341.html
>
> Generall you should provide all reasonable information in the changelog
> instead of linking to it.
will apply this, thanks.
>
>> + if (sip->i_d.di_nlink == 0)
>> + tres = &M_RES(mp)->tr_link_tmpfile;
>> + else
>> + tres = &M_RES(mp)->tr_link;
>
> As mentioned before I think Dave wanted you to always use the same
> reservation, but I'll leave that discussion to him.
If as you said, when some tons of regular files are created, it won't
waste some disk space? e.g. some files want to reserve some space, but
get NOSPACE due to other files reserving additional space?
>
>> +/* For creating a link to an O_TMPFILE inode, except modifying
>> + * those metadata for regular inode, we still need to remove an inode
>> + * from unlinked list at first. That is, we can modify:
>> + * the agi hash list and counters: sector size
>> + * the on disk inode before ours in the agi hash list: inode cluster size
>> + */
>
> We always have an emptry content
Done, thanks.
>
> /*
>
> line at the beginning of comments in XFS and the Linux kernel in
> general.
>
--
Regards,
Zhi Yong Wu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists