xfs
[Top] [All Lists]

Re: [PATCH] logprint: Fix printing of AGF buffers

To: Jan Kara <jack@xxxxxxx>
Subject: Re: [PATCH] logprint: Fix printing of AGF buffers
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 15 Jul 2014 08:39:22 -0700
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140715140938.GA1733@xxxxxxxxxxxxx>
References: <1405349100-19734-1-git-send-email-jack@xxxxxxx> <20140715101931.GC30363@xxxxxxxxxxxxx> <20140715140938.GA1733@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
On Tue, Jul 15, 2014 at 04:09:38PM +0200, Jan Kara wrote:
>   I had a look before I submitted this patch and I didn't find anything.
> Now that I'm looking again, AGI buffers probably need a similar treatment.
> Superblock buffers are already checked against fixed number so those don't
> have a problem. Dquot buffers should be fine as well because those don't
> have a checksum and other unlogged stuff. And I didn't find any other
> structures in the log that would have the problem (please point me if I
> missed something).
> 
> Regarding how to fix this cleanly - offsetof() seems like a reasonably
> clean way to me. If you prefer to define number of bytes each buffer type
> has to have in the log, I can do that as well. Or I could define
> alternative structures only containing fields we need in the log so that we
> can print info but this all seems like an additional complexity with
> disputable gain...

I've taken a bit of a closer log (OMG, what a mess logprint is..), and
it seems at least in this are the AGF and AGI are affected of the struct
growth in v4.

It seems like in this specific case using your offsetoff trick is
fine, it just needs a good comment explaining it.

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