mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Athira Rajeev <atrajeev@linux.ibm.com>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	jiang.peng9@zte.com.cn, shao.mingyin@zte.com.cn,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [mainline]tools/perf build warnings
Date: Wed, 16 Apr 2025 19:49:38 +0530	[thread overview]
Message-ID: <99a06f56-08cf-42ce-a231-f9a38c6ece9a@linux.ibm.com> (raw)
In-Reply-To: <1ec497ed-b98c-46aa-a9c2-5fa906790298@linux.ibm.com>


On 16/04/25 7:33 pm, Venkat Rao Bagalkote wrote:
>
> On 16/04/25 6:41 pm, Athira Rajeev wrote:
>>
>>> On 16 Apr 2025, at 5:12 PM, Venkat Rao Bagalkote 
>>> <venkat88@linux.ibm.com> wrote:
>>>
>>> Hello,
>>>
>>>
>>> I am observing a new build warning on today mainline kernel, with 
>>> head commit: g834a4a689699
>>>
>>> Repo:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>
>>>
>>> Warnings:
>>>
>>> diff -u tools/include/vdso/unaligned.h include/vdso/unaligned.h
>>>
>>>
>>> If you happen to fix this, please add below tag.
>>>
>>>
>>> Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>> Hi Venkat
>>
>> Can you please check with 
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/?h=tmp.perf-tools-next
>> with the tmp.perf-tools-next branch..
>
>
> I verified with perf-tools-next repo on both branches namely 
> tmp.perf-tools-next and perf-tools-next, and I think this warning got 
> recently introduced.

/Typo in the last mail, please refer to below update./

I verified with perf-tools-next repo on both branches namely 
tmp.perf-tools-next and perf-tools-next, and issue is not seen there. 
And I think this warning got recently introduced.

>
> Git Bisect is pointing to acea9943271b62905033f2f8ca571cdd52d6ea7b as 
> first bad commit.
>
>
> Below is the bisect log:
>
> git bisect log
> git bisect start
> # status: waiting for both good and bad commits
> # bad: [834a4a689699090a406d1662b03affa8b155d025] Merge tag 
> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
> git bisect bad 834a4a689699090a406d1662b03affa8b155d025
> # status: waiting for good commit(s), bad commit known
> # good: [0af2f6be1b4281385b618cb86ad946eded089ac8] Linux 6.15-rc1
> git bisect good 0af2f6be1b4281385b618cb86ad946eded089ac8
> # bad: [ef7785882672e73847fb80f6c39e76998d4db57b] Merge tag 
> 'bcachefs-2025-04-10' of git://evilpiepirate.org/bcachefs
> git bisect bad ef7785882672e73847fb80f6c39e76998d4db57b
> # good: [e4742a89cfaced383db758bef94037637899487a] Merge tag 
> 'block-6.15-20250410' of git://git.kernel.dk/linux
> git bisect good e4742a89cfaced383db758bef94037637899487a
> # good: [eaa517b77e63442260640d875f824d1111ca6569] ethtool: cmis_cdb: 
> Fix incorrect read / write length extension
> git bisect good eaa517b77e63442260640d875f824d1111ca6569
> # good: [ac253a537da3b210fa4b65d522d5533fc68f9515] Merge tag 
> 'perf-urgent-2025-04-10' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> git bisect good ac253a537da3b210fa4b65d522d5533fc68f9515
> # good: [3c9de67dd37029cca1d0f391ff565b3809b40a1f] Merge tag 
> 'x86-urgent-2025-04-10' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> git bisect good 3c9de67dd37029cca1d0f391ff565b3809b40a1f
> # bad: [0c7cae12f67c4c5fd232cffb27023deb409e1e20] Merge tag 
> 'irq-urgent-2025-04-10' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> git bisect bad 0c7cae12f67c4c5fd232cffb27023deb409e1e20
> # bad: [34833819d2270ef96fa98fe3c1d3d297b5dec986] Merge tag 
> 'timers-urgent-2025-04-10' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> git bisect bad 34833819d2270ef96fa98fe3c1d3d297b5dec986
> # good: [92e250c624ea37fde64bfd624fd2556f0d846f18] timekeeping: Add a 
> lockdep override in tick_freeze()
> git bisect good 92e250c624ea37fde64bfd624fd2556f0d846f18
> # bad: [acea9943271b62905033f2f8ca571cdd52d6ea7b] vdso: Address 
> variable shadowing in macros
> git bisect bad acea9943271b62905033f2f8ca571cdd52d6ea7b
> # first bad commit: [acea9943271b62905033f2f8ca571cdd52d6ea7b] vdso: 
> Address variable shadowing in macros
>
>
> Regards,
>
> Venkat.
>
>>
>> Also there is a patchset here:
>> https://lore.kernel.org/linux-perf-users/FE96FD04-4396-4C34-A70D-2A592FD5F916@linux.ibm.com/T/#m3e9d6aac4c34ebf42f18f3c213b7dff8f8c70d9d 
>>
>>
>> Which I think you have already tested..
>>
>> Thanks
>> Athira
>>>
>>> Regards,
>>>
>>> Venkat.
>>>
>>>
>>>

  reply	other threads:[~2025-04-16 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:42 Venkat Rao Bagalkote
2025-04-16 13:11 ` Athira Rajeev
2025-04-16 14:03   ` Venkat Rao Bagalkote
2025-04-16 14:19     ` Venkat Rao Bagalkote [this message]
2025-04-16 14:34       ` Athira Rajeev
2025-04-16 17:16         ` Venkat Rao Bagalkote
2025-04-17  2:01           ` jiang.peng9
2025-04-17  2:45             ` Arnaldo Carvalho de Melo
2025-04-17  3:13               ` jiang.peng9

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=99a06f56-08cf-42ce-a231-f9a38c6ece9a@linux.ibm.com \
    --to=venkat88@linux.ibm.com \
    --cc=atrajeev@linux.ibm.com \
    --cc=jiang.peng9@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=shao.mingyin@zte.com.cn \
    --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

all inboxes | Powered by JetHome®