public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the btrfs tree
Date: Tue, 12 Sep 2023 10:46:46 +1000	[thread overview]
Message-ID: <20230912104646.3a9140f7@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2573 bytes --]

Hi all,

After merging the btrfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:

In file included from include/linux/swab.h:5,
                 from include/uapi/linux/byteorder/big_endian.h:14,
                 from include/linux/byteorder/big_endian.h:5,
                 from arch/powerpc/include/uapi/asm/byteorder.h:14,
                 from include/asm-generic/bitops/le.h:6,
                 from arch/powerpc/include/asm/bitops.h:336,
                 from include/linux/bitops.h:68,
                 from fs/btrfs/extent_io.c:3:
In function 'btrfs_disk_key_to_cpu',
    inlined from 'btrfs_item_key_to_cpu' at fs/btrfs/accessors.h:648:2,
    inlined from 'fiemap_find_last_extent_offset' at fs/btrfs/extent_io.c:2804:2,
    inlined from 'extent_fiemap' at fs/btrfs/extent_io.c:2879:8:
include/uapi/linux/swab.h:128:28: warning: 'disk_key.objectid' may be used uninitialized [-Wmaybe-uninitialized]
  128 | #define __swab64(x) (__u64)__builtin_bswap64((__u64)(x))
      |                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/uapi/linux/byteorder/big_endian.h:33:26: note: in expansion of macro '__swab64'
   33 | #define __le64_to_cpu(x) __swab64((__force __u64)(__le64)(x))
      |                          ^~~~~~~~
include/linux/byteorder/generic.h:87:21: note: in expansion of macro '__le64_to_cpu'
   87 | #define le64_to_cpu __le64_to_cpu
      |                     ^~~~~~~~~~~~~
fs/btrfs/accessors.h:622:25: note: in expansion of macro 'le64_to_cpu'
  622 |         cpu->objectid = le64_to_cpu(disk->objectid);
      |                         ^~~~~~~~~~~
In file included from fs/btrfs/extent_io.c:34:
fs/btrfs/accessors.h: In function 'extent_fiemap':
fs/btrfs/accessors.h:645:31: note: 'disk_key.objectid' was declared here
  645 |         struct btrfs_disk_key disk_key;
      |                               ^~~~~~~~
In function 'fiemap_find_last_extent_offset',
    inlined from 'extent_fiemap' at fs/btrfs/extent_io.c:2879:8:
fs/btrfs/extent_io.c:2805:33: warning: 'disk_key.type' may be used uninitialized [-Wmaybe-uninitialized]
 2805 |         if (key.objectid != ino || key.type != BTRFS_EXTENT_DATA_KEY) {
fs/btrfs/accessors.h: In function 'extent_fiemap':
fs/btrfs/accessors.h:645:31: note: 'disk_key.type' was declared here
  645 |         struct btrfs_disk_key disk_key;
      |                               ^~~~~~~~

I don't really have any idea what caused this (it *may* have been my
change from gcc v12 to v13?).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-09-12  3:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  0:46 Stephen Rothwell [this message]
2023-09-12 11:20 ` linux-next: build warnings after merge of the btrfs tree David Sterba
2023-09-12 12:20   ` Stephen Rothwell
2023-09-20  3:16     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-01-27  1:36 Stephen Rothwell
2020-01-14 22:30 Stephen Rothwell
2020-01-17 16:24 ` David Sterba

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=20230912104646.3a9140f7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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