xfs
[Top] [All Lists]

Re: [PATCH 16/71] xfs: log refcount intent items

To: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Subject: Re: [PATCH 16/71] xfs: log refcount intent items
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 11 Sep 2016 05:52:46 -0700
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160908231656.GC8969@xxxxxxxxxxxxxxxx>
References: <147216791538.867.12413509832420924168.stgit@xxxxxxxxxxxxxxxx> <147216802075.867.12945255918683675311.stgit@xxxxxxxxxxxxxxxx> <20160906152155.GJ24287@xxxxxxxxxxxxx> <20160908191404.GB8969@xxxxxxxxxxxxxxxx> <20160908231326.GA30056@dastard> <20160908231656.GC8969@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.6.1 (2016-04-27)
On Thu, Sep 08, 2016 at 04:16:56PM -0700, Darrick J. Wong wrote:
> > Carfeul there - enums are not defined to have a fixed size and so
> > can change from compiler version to compiler version. IOWs, the
> > enum values can be written idirectly to an on-disk structure, but
> > the on-disk structure should not be using the enum as the type
> > definition for whatever gets stored on disk.
> 
> <nod>  I left the fields (and the #define flags) definitions alone,
> so it's only writing enum values indirectly into a fixed size (u32)
> variable on-disk.
> 
> i.e. I'm not using enums in the on-disk structure definitions.

now add a byte swap for the flags and everything should be fine.
The whole idea of architecture-dependent log items was a horrible
idea, and I still have hopes of fixing it eventually.

<Prev in Thread] Current Thread [Next in Thread>