From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Gao Xiang <xiang@kernel.org>,
Chao Yu <chao@kernel.org>,
linux-erofs@lists.ozlabs.org, Bo Liu <liubo03@inspur.com>
Subject: Re: linux-next: Tree for Jul 21 (fs/erofs/*.c)
Date: Mon, 21 Jul 2025 14:31:25 -0700 [thread overview]
Message-ID: <b555f01c-4e9e-4b42-aa5a-2d35ef9c1c50@infradead.org> (raw)
In-Reply-To: <20250721174126.75106f39@canb.auug.org.au>
On 7/21/25 12:41 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20250718:
>
on i386 (i.e., 32-bit):
In file included from ../include/linux/bits.h:5,
from ../include/linux/string_helpers.h:5,
from ../include/linux/seq_file.h:7,
from ../fs/erofs/super.c:8:
../fs/erofs/internal.h: In function 'erofs_inode_in_metabox':
../include/vdso/bits.h:7:40: warning: left shift count >= width of type [-Wshift-count-overflow]
7 | #define BIT(nr) (UL(1) << (nr))
| ^~
../fs/erofs/internal.h:305:38: note: in expansion of macro 'BIT'
305 | return EROFS_I(inode)->nid & BIT(EROFS_DIRENT_NID_METABOX_BIT);
| ^~~
Only super.c is shown here, but the warnings happen any time that the macro:
#define EROFS_DIRENT_NID_METABOX_BIT 63
is used (on 32-bit), all (or mostly) from internal.h erofs_nid_to_ino64():
return ((nid << 1) & GENMASK_ULL(63, 32)) | (nid & GENMASK(30, 0)) |
((nid >> EROFS_DIRENT_NID_METABOX_BIT) << 31);
--
~Randy
next prev parent reply other threads:[~2025-07-21 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 7:41 linux-next: Tree for Jul 21 Stephen Rothwell
2025-07-21 20:17 ` linux-next: Tree for Jul 21 [drivers/gpu/drm/xe/xe.ko] Randy Dunlap
2025-07-22 1:38 ` Lucas De Marchi
2025-07-22 5:50 ` Randy Dunlap
2025-07-22 13:26 ` Lucas De Marchi
2025-07-23 15:50 ` Lucas De Marchi
2025-07-21 21:31 ` Randy Dunlap [this message]
2025-07-22 0:43 ` linux-next: Tree for Jul 21 (fs/erofs/*.c) Gao Xiang
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=b555f01c-4e9e-4b42-aa5a-2d35ef9c1c50@infradead.org \
--to=rdunlap@infradead.org \
--cc=chao@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=sfr@canb.auug.org.au \
--cc=xiang@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;
as well as URLs for NNTP newsgroup(s).