From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings after merge of the tip tree
Date: Fri, 23 Jun 2017 14:19:13 +1000 [thread overview]
Message-ID: <20170623141913.322b0062@canb.auug.org.au> (raw)
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:
In file included from arch/x86/include/asm/paravirt_types.h:44:0,
from arch/x86/include/asm/ptrace.h:71,
from arch/x86/include/asm/math_emu.h:4,
from arch/x86/include/asm/processor.h:11,
from arch/x86/include/asm/cpufeature.h:4,
from arch/x86/include/asm/thread_info.h:52,
from include/linux/thread_info.h:37,
from arch/x86/include/asm/preempt.h:6,
from include/linux/preempt.h:80,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:35,
from include/linux/time.h:5,
from include/uapi/linux/timex.h:56,
from include/linux/timex.h:56,
from include/linux/clocksource.h:12,
from arch/x86/include/asm/vgtod.h:5,
from arch/x86/entry/vdso/vdso32/../vclock_gettime.c:15,
from arch/x86/entry/vdso/vdso32/vclock_gettime.c:32:
arch/x86/include/asm/pgtable.h: In function 'pte_flags_pkey':
arch/x86/include/asm/pgtable_types.h:56:43: warning: left shift count >= width of type [-Wshift-count-overflow]
#define _PAGE_PKEY_BIT0 (_AT(pteval_t, 1) << _PAGE_BIT_PKEY_BIT0)
^
arch/x86/include/asm/pgtable_types.h:68:26: note: in expansion of macro '_PAGE_PKEY_BIT0'
#define _PAGE_PKEY_MASK (_PAGE_PKEY_BIT0 | \
^
arch/x86/include/asm/pgtable.h:1187:22: note: in expansion of macro '_PAGE_PKEY_MASK'
return (pte_flags & _PAGE_PKEY_MASK) >> _PAGE_BIT_PKEY_BIT0;
^
arch/x86/include/asm/pgtable_types.h:57:43: warning: left shift count >= width of type [-Wshift-count-overflow]
#define _PAGE_PKEY_BIT1 (_AT(pteval_t, 1) << _PAGE_BIT_PKEY_BIT1)
^
arch/x86/include/asm/pgtable_types.h:69:5: note: in expansion of macro '_PAGE_PKEY_BIT1'
_PAGE_PKEY_BIT1 | \
^
arch/x86/include/asm/pgtable.h:1187:22: note: in expansion of macro '_PAGE_PKEY_MASK'
return (pte_flags & _PAGE_PKEY_MASK) >> _PAGE_BIT_PKEY_BIT0;
^
arch/x86/include/asm/pgtable_types.h:58:43: warning: left shift count >= width of type [-Wshift-count-overflow]
#define _PAGE_PKEY_BIT2 (_AT(pteval_t, 1) << _PAGE_BIT_PKEY_BIT2)
^
arch/x86/include/asm/pgtable_types.h:70:5: note: in expansion of macro '_PAGE_PKEY_BIT2'
_PAGE_PKEY_BIT2 | \
^
arch/x86/include/asm/pgtable.h:1187:22: note: in expansion of macro '_PAGE_PKEY_MASK'
return (pte_flags & _PAGE_PKEY_MASK) >> _PAGE_BIT_PKEY_BIT0;
^
arch/x86/include/asm/pgtable_types.h:59:43: warning: left shift count >= width of type [-Wshift-count-overflow]
#define _PAGE_PKEY_BIT3 (_AT(pteval_t, 1) << _PAGE_BIT_PKEY_BIT3)
^
arch/x86/include/asm/pgtable_types.h:71:5: note: in expansion of macro '_PAGE_PKEY_BIT3'
_PAGE_PKEY_BIT3)
^
arch/x86/include/asm/pgtable.h:1187:22: note: in expansion of macro '_PAGE_PKEY_MASK'
return (pte_flags & _PAGE_PKEY_MASK) >> _PAGE_BIT_PKEY_BIT0;
^
In file included from include/linux/kasan.h:16:0,
from include/linux/slab.h:120,
from include/linux/irq.h:25,
from arch/x86/include/asm/hardirq.h:5,
from include/linux/hardirq.h:8,
from include/linux/interrupt.h:12,
from arch/x86/include/asm/mshyperv.h:5,
from arch/x86/entry/vdso/vdso32/../vclock_gettime.c:20,
from arch/x86/entry/vdso/vdso32/vclock_gettime.c:32:
arch/x86/include/asm/pgtable.h:1187:39: warning: right shift count >= width of type [-Wshift-count-overflow]
return (pte_flags & _PAGE_PKEY_MASK) >> _PAGE_BIT_PKEY_BIT0;
^
I have no idea what caused this.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-06-23 4:19 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 4:19 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 3:59 linux-next: build warnings after merge of the tip tree Stephen Rothwell
2023-12-01 0:29 Stephen Rothwell
2023-12-01 12:09 ` Uros Bizjak
2023-12-04 4:08 ` Stephen Rothwell
2023-12-04 7:02 ` Uros Bizjak
2023-12-11 5:19 ` Stephen Rothwell
2023-12-11 7:06 ` Uros Bizjak
2023-06-02 3:12 Stephen Rothwell
2022-11-21 7:41 Stephen Rothwell
2022-05-20 7:49 Stephen Rothwell
2022-04-27 0:10 Stephen Rothwell
2022-04-27 11:31 ` Borislav Petkov
2022-04-27 13:43 ` Tom Lendacky
2022-03-22 3:51 Stephen Rothwell
2022-03-22 21:52 ` Peter Zijlstra
2022-03-22 23:11 ` Stephen Rothwell
2022-03-21 3:03 Stephen Rothwell
2022-03-21 12:55 ` Peter Zijlstra
2022-03-21 13:04 ` Peter Zijlstra
2022-03-21 13:08 ` Peter Zijlstra
2022-03-21 13:45 ` Peter Zijlstra
2022-03-21 14:19 ` Mark Rutland
2022-03-21 15:28 ` Peter Zijlstra
2022-03-21 15:45 ` Peter Zijlstra
2022-03-21 16:37 ` Linus Torvalds
2022-03-21 16:44 ` Peter Zijlstra
2022-03-21 16:52 ` Linus Torvalds
2022-03-21 22:05 ` Stephen Rothwell
2022-03-21 22:12 ` Alexei Starovoitov
2022-03-21 22:46 ` Stephen Rothwell
2022-03-21 22:50 ` Alexei Starovoitov
2022-03-21 22:55 ` Steven Rostedt
2022-03-22 4:51 ` Masami Hiramatsu
2022-03-22 4:53 ` Alexei Starovoitov
2022-03-22 7:42 ` Peter Zijlstra
2022-03-22 4:38 ` Masami Hiramatsu
2022-03-21 15:28 ` Steven Rostedt
2022-03-21 16:04 ` Peter Zijlstra
2022-03-21 16:12 ` Steven Rostedt
2022-03-21 16:15 ` Steven Rostedt
2022-03-21 16:22 ` Steven Rostedt
2022-03-21 16:39 ` Steven Rostedt
2022-03-21 16:40 ` Peter Zijlstra
2022-03-21 16:45 ` Steven Rostedt
2022-03-21 16:50 ` Peter Zijlstra
2022-03-21 16:54 ` Steven Rostedt
2022-03-22 7:54 ` Peter Zijlstra
2022-03-22 13:12 ` Steven Rostedt
2022-03-22 14:35 ` Peter Zijlstra
2022-03-22 15:04 ` Steven Rostedt
2022-03-22 15:19 ` Peter Zijlstra
2022-03-22 15:48 ` Peter Zijlstra
2022-03-22 16:17 ` Steven Rostedt
2022-03-23 2:23 ` Masami Hiramatsu
2022-03-23 2:42 ` Steven Rostedt
2022-03-23 6:28 ` Masami Hiramatsu
2022-03-22 14:25 ` Masami Hiramatsu
2022-03-21 16:48 ` Peter Zijlstra
2022-03-22 5:31 ` Masami Hiramatsu
2022-03-22 8:08 ` Peter Zijlstra
2022-03-22 9:14 ` Masami Hiramatsu
2022-03-22 12:07 ` Peter Zijlstra
2022-03-22 12:17 ` Peter Zijlstra
2022-03-22 12:46 ` Masami Hiramatsu
2022-03-22 13:22 ` Steven Rostedt
2022-03-22 13:15 ` Mark Rutland
2022-03-22 13:51 ` Masami Hiramatsu
2022-03-22 10:46 ` Peter Zijlstra
2022-03-22 10:59 ` Peter Zijlstra
2021-12-17 3:40 Stephen Rothwell
2022-01-21 23:58 ` Stephen Rothwell
2022-03-15 2:32 ` Stephen Rothwell
2022-04-04 3:26 ` Stephen Rothwell
2021-10-12 10:20 Stephen Rothwell
2021-10-12 13:58 ` André Almeida
2020-11-30 7:05 Stephen Rothwell
2020-11-30 10:17 ` Borislav Petkov
2020-11-30 21:56 ` Ernst, Justin
2020-11-30 22:18 ` Borislav Petkov
2020-11-23 7:19 Stephen Rothwell
2020-11-23 23:03 ` Jarkko Sakkinen
2017-11-02 2:53 Stephen Rothwell
2017-11-03 21:00 ` Masami Hiramatsu
2017-11-04 8:01 ` Ingo Molnar
2017-11-04 12:16 ` Masami Hiramatsu
2017-11-13 11:31 ` Stephen Rothwell
2016-07-14 3:49 Stephen Rothwell
2016-07-14 3:37 Stephen Rothwell
2016-07-14 4:18 ` Stephen Rothwell
2012-10-12 5:11 Stephen Rothwell
2011-01-31 4:27 Stephen Rothwell
2011-01-31 5:08 ` Jaswinder Singh
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=20170623141913.322b0062@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).