| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: [patch] remove xattr buffer size dependency on page size in xfsdump |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 22 May 2008 09:28:41 -0400 |
| Cc: | xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20080522061402.GS173056135@xxxxxxx> |
| References: | <20080522061402.GS173056135@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Thu, May 22, 2008 at 04:14:02PM +1000, David Chinner wrote: > > The extended attr buffer size used by xfsdump is based on page size. > The maximum buffer size the kernel will accept is 64k. On a 64k page > machine, the default buffer size will be rejected by the kernel, thereby > breaking dump and restore. > > Limit the buffer size to XATTR_LIST_MAX in dump, restore and libhandle > so the kernel won't reject otherwise valid requests. I suspect this will break on non-linux platforms because XATTR_LIST_MAX is only in the Linux headers. With a precaution, e.g. by keeping the old behaviour when XATTR_LIST_MAX is not defined this looks good. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch] xfsqa test to check log size scaling, Christoph Hellwig |
|---|---|
| Next by Date: | Re: TAKE streamline init/exit path, Christoph Hellwig |
| Previous by Thread: | [patch] remove xattr buffer size dependency on page size in xfsdump, David Chinner |
| Next by Thread: | [hack] allow xfsrestore to run on 64k page size machines, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |