From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: Build Warnings at arch/powerpc/
Date: Tue, 4 Mar 2025 17:11:19 +0530 [thread overview]
Message-ID: <2a8656cf-8ff5-40fa-8ed8-efb1245fddf2@linux.ibm.com> (raw)
In-Reply-To: <47aa8b75-96b6-4e37-bb62-ad758b414076@linux.ibm.com>
Hello Maddy,
Git bisect is poinitng to d543c29a68989ac9e39e0b50cfe8b592d92a1599 as
the first bad commit.
Git Bisect log:
[root@ltc-zzci-1 linux-next]# git bisect log
git bisect start
# status: waiting for both good and bad commits
# good: [7eb172143d5508b4da468ed59ee857c6e5e01da6] Linux 6.14-rc5
git bisect good 7eb172143d5508b4da468ed59ee857c6e5e01da6
# status: waiting for bad commit, 1 good commit known
# bad: [cd3215bbcb9d4321def93fea6cfad4d5b42b9d1d] Add linux-next
specific files for 20250303
git bisect bad cd3215bbcb9d4321def93fea6cfad4d5b42b9d1d
# bad: [f084774e60dd4171a536e7f5506f90031e3a8c6f] Merge branch
'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
git bisect bad f084774e60dd4171a536e7f5506f90031e3a8c6f
# good: [a57419b6b3df381d61367a3034910d1d8a197fd7] Merge branch
'fs-next' of linux-next
git bisect good a57419b6b3df381d61367a3034910d1d8a197fd7
# good: [4350f3677257b7762a89901f81bc2e5ef84bc30f] Merge branch
'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git
git bisect good 4350f3677257b7762a89901f81bc2e5ef84bc30f
# good: [e87700965abeddcdb84c9540107c69ce08b87431] Merge tag
'for-netdev' of https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next
git bisect good e87700965abeddcdb84c9540107c69ce08b87431
# bad: [0edfdc95d3459a6a9e9487a748b04c5b8fd2a69a] Merge branch 'master'
of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
git bisect bad 0edfdc95d3459a6a9e9487a748b04c5b8fd2a69a
# good: [97fc6863637630cdf9a5e9ed2569fe9a7974434b] net: usb: cdc_mbim:
fix Telit Cinterion FE990A name
git bisect good 97fc6863637630cdf9a5e9ed2569fe9a7974434b
# good: [bb7abf3049025f7e4ad91cff2d9fe8381a9278af] bpf: make
state->dfs_depth < state->loop_entry->dfs_depth an invariant
git bisect good bb7abf3049025f7e4ad91cff2d9fe8381a9278af
# good: [0ba0ef012eba63652a50b318a7a3136963c37f74] selftests/bpf: Test
bpf_usdt_arg_size() function
git bisect good 0ba0ef012eba63652a50b318a7a3136963c37f74
# good: [42c5e6d2accf31bba4cd31f8a742d5b9e19a7d28] selftests/bpf: Add
selftests allowing cgroup prog pre-ordering
git bisect good 42c5e6d2accf31bba4cd31f8a742d5b9e19a7d28
# good: [b70c222ea9d66d51fc1f038f82e41ea17b38499f] Merge branch
'bpf-next/master' into for-next
git bisect good b70c222ea9d66d51fc1f038f82e41ea17b38499f
# good: [cc18f482e8b60a2bcf2d7d57b48740bd0837fc04] xfrm: provide common
xdo_dev_offload_ok callback implementation
git bisect good cc18f482e8b60a2bcf2d7d57b48740bd0837fc04
# bad: [d543c29a68989ac9e39e0b50cfe8b592d92a1599] Merge branch
'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
git bisect bad d543c29a68989ac9e39e0b50cfe8b592d92a1599
# good: [3ab37b090d1c458553a5268c7aaa8790ee759674] Merge branch 'main'
of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
git bisect good 3ab37b090d1c458553a5268c7aaa8790ee759674
# first bad commit: [d543c29a68989ac9e39e0b50cfe8b592d92a1599] Merge
branch 'for-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
On 04/03/25 11:43 am, Madhavan Srinivasan wrote:
>
> On 3/4/25 10:42 AM, Venkat Rao Bagalkote wrote:
>> Greetings!!
>>
>>
>> Observing build warnings with linux-next and powerpc repo's. Issue is currently not seen on mainline yet.
>>
>> PPC Repo: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git merge branch
>>
>> PPC Kernel Version: 6.14.0-rc4-g1304f486dbf1
>> next Repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch
>>
>> next Kernel Version: 6.14.0-rc5-next-20250303
>>
>>
>> On linux-next kernel issue got introduced b/w next-20250227 and next-20250303
>>
>>
>> Build Warnings:
>>
>> arch/powerpc/kvm/book3s_hv_rmhandlers.o: warning: objtool: .text+0xe84: intra_function_call not a direct call
>> arch/powerpc/crypto/ghashp8-ppc.o: warning: objtool: .text+0x22c: unannotated intra-function call
>> arch/powerpc/kernel/switch.o: warning: objtool: .text+0x4: intra_function_call not a direct call
>>
>>
> Can you please specific the compiler and compiler version you found this issue with
>
> maddy
GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
>
>> If you fix this issue, please add below tag.
>>
>>
>> Reported-By: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
>>
>>
>> Regards,
>>
>> Venkat.
>>
Regards,
Venkat.
>
prev parent reply other threads:[~2025-03-04 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 5:12 Build Warnings at arch/powerpc/ Venkat Rao Bagalkote
2025-03-04 6:13 ` Madhavan Srinivasan
2025-03-04 8:56 ` Christophe Leroy
2025-03-04 11:28 ` Madhavan Srinivasan
2025-03-04 12:38 ` Madhavan Srinivasan
2025-03-04 13:03 ` Venkat Rao Bagalkote
2025-03-04 13:13 ` Christophe Leroy
2025-03-04 15:44 ` Venkat Rao Bagalkote
2025-03-04 17:17 ` Christophe Leroy
2025-03-04 13:06 ` Christophe Leroy
2025-03-04 11:41 ` Venkat Rao Bagalkote [this message]
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=2a8656cf-8ff5-40fa-8ed8-efb1245fddf2@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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).