mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
To: hch <hch@lst.de>
Cc: "djwong@kernel.org" <djwong@kernel.org>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"cem@kernel.org" <cem@kernel.org>
Subject: Re: [PATCH] xfs: add static size checks for structures in xfs_fs.h
Date: Tue, 10 Feb 2026 05:59:36 +0000	[thread overview]
Message-ID: <ab478aaa3504c366f6a36cb06293fb1a2f1320bc.camel@wdc.com> (raw)
In-Reply-To: <20260209144749.GB16995@lst.de>

[snip]...
> 
> Out of the Linux supported architectures there are basically five
> kinds of differences a struct ABI can have:
> 
>  1) different pointer sizes
>  2) different size of long for long derived types
>  3) different alignment of u64 on i386 vs everyone else
>  4) different alignment of u16 on arm32-oldabi vs everyone else
>  5) configuration dependencies
> 
> 5) is a no-go for exported types
> 
> 4) doesn't happen in the current xfs uapi headers (it happens in on-
> disk
> formats structs though..).
> 
> 3) is clearly indicated by the x86-specific handlers in xfs_ioctl32.c
> 
> 2) and 1) are indicated by the other handlers in xfs_ioctl32.c.
> 
> Based on that your above list is a good start, but incomplete.
> The list of compat_ structures in fs/xfs/xfs_ioctl32.h should have
> a complete list, and if doesn't that is a bug as we're missing
> compat handlers.

Thanks! I've removed all of the compat__ structs listed in
xfs_ioctl32.h for V2 that was in V1. Compiling for i386 tested okay.

Wilfred

  reply	other threads:[~2026-02-10  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  3:05 Wilfred Mallawa
2026-02-06  6:08 ` Christoph Hellwig
2026-02-09  7:04   ` Wilfred Mallawa
2026-02-09 14:47     ` hch
2026-02-10  5:59       ` Wilfred Mallawa [this message]
2026-02-06  9:39 ` kernel test robot
2026-02-06 11:02 ` kernel test robot
2026-02-06 18:03 ` kernel test robot
2026-02-06 22:27 ` Dave Chinner
2026-02-09  6:57   ` Wilfred Mallawa
2026-02-09 14:41   ` Christoph Hellwig

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=ab478aaa3504c366f6a36cb06293fb1a2f1320bc.camel@wdc.com \
    --to=wilfred.mallawa@wdc.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®