From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Move struct gfs2_rgrp_lvb out of gfs2_ondisk.h
Date: Wed, 15 Jan 2020 09:49:59 +0000 [thread overview]
Message-ID: <62faa428-a933-4848-d897-deb038078ac3@redhat.com> (raw)
In-Reply-To: <CAHc6FU6UrNOenH6swABCOU2ZTh5NUfns-QeA29PSDsMwxFA1sQ@mail.gmail.com>
Hi,
On 15/01/2020 09:24, Andreas Gruenbacher wrote:
> On Wed, Jan 15, 2020 at 9:58 AM Steven Whitehouse <swhiteho@redhat.com> wrote:
>> On 15/01/2020 08:49, Andreas Gruenbacher wrote:
>>> There's no point in sharing the internal structure of lock value blocks
>>> with user space.
>> The reason that is in ondisk is that changing that structure is
>> something that needs to follow the same rules as changing the on disk
>> structures. So it is there as a reminder of that,
> I can see a point in that. The reason I've posted this is because Bob
> was complaining that changes to include/uapi/linux/gfs2_ondisk.h break
> his out-of-tree module build process. (One of the patches I'm working
> on adds an inode LVB.) The same would be true of on-disk format
> changes as well of course, and those definitely need to be shared with
> user space. I'm not usually building gfs2 out of tree, so I'm
> indifferent to this change.
>
> Thanks,
> Andreas
>
Why would we need to be able to build gfs2 (at least I assume it is
gfs2) out of tree anyway?
Steve.
next prev parent reply other threads:[~2020-01-15 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 8:49 [Cluster-devel] [PATCH] Move struct gfs2_rgrp_lvb out of gfs2_ondisk.h Andreas Gruenbacher
2020-01-15 8:58 ` Steven Whitehouse
2020-01-15 9:24 ` Andreas Gruenbacher
2020-01-15 9:49 ` Steven Whitehouse [this message]
2020-01-15 13:19 ` Bob Peterson
2020-01-15 15:26 ` Andrew Price
2020-01-15 15:43 ` Andrew Price
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62faa428-a933-4848-d897-deb038078ac3@redhat.com \
--to=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).