From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Clark Williams <williams@redhat.com>,
Kate Carcia <kcarcia@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Sohom Datta <sohomdatta1+git@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL] perf tools fixes for v6.2: 3rd batch
Date: Thu, 19 Jan 2023 22:27:50 -0300 [thread overview]
Message-ID: <Y8nuFmDDQU5c/4tS@kernel.org> (raw)
In-Reply-To: <20230119171510.166368-1-acme@kernel.org>
Humm,
I'm not finding this on the lkml archives, so please ignore it
if this is going as a duplicate for anyone :-\
Thanks,
- Arnaldo
Em Thu, Jan 19, 2023 at 02:15:10PM -0300, Arnaldo Carvalho de Melo escreveu:
> Hi Linus,
>
> Sync of UAPI headers with the kernel sources, to address
> warnings while building perf and two small fixes for the main tools + a
> 'perf test' fix related to the build-id fix.
>
> Please consider pulling,
>
> Best regards,
>
> - Arnaldo
>
> The following changes since commit c1649ec55708ae42091a2f1bca1ab49ecd722d55:
>
> Merge tag 'nfsd-6.2-4' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux (2023-01-17 09:29:17 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v6.2-3-2023-01-19
>
> for you to fetch changes up to 3d9c07c4cfc06cf7927cd00c04dffd1165d03c53:
>
> perf test build-id: Fix test check for PE file (2023-01-18 10:52:06 -0300)
>
> ----------------------------------------------------------------
> perf tools fixes for v6.2: 3rd batch.
>
> - Prevent reading into undefined memory in the expression lexer,
> accounting for a trailer backslash followed by the null byte.
>
> - Fix file mode when copying files to the build id cache, the problem
> happens when the cache directory is in a different file system than the
> file being cached, otherwise the mode was preserved as only a hard link
> would be done to save space.
>
> - Fix a related build-id 'perf test' entry that checked that permission
> when caching PE (Portable Executable) files, used when profiling
> Windows executables under wine.
>
> - Sync the tools/ copies of kvm headers, build_bug.h, socket.h and
> arm64's cputype.h with the kernel sources.
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Arnaldo Carvalho de Melo (6):
> tools headers UAPI: Sync linux/kvm.h with the kernel sources
> tools headers UAPI: Sync x86's asm/kvm.h with the kernel sources
> tools kvm headers arm64: Update KVM header from the kernel sources
> tools headers arm64: Sync arm64's cputype.h with the kernel sources
> perf beauty: Update copy of linux/socket.h with the kernel sources
> tools headers: Syncronize linux/build_bug.h with the kernel sources
>
> Athira Rajeev (2):
> perf buildid-cache: Fix the file mode with copyfile() while adding file to build-id cache
> perf test build-id: Fix test check for PE file
>
> Sohom Datta (1):
> perf expr: Prevent normalize() from reading into undefined memory in the expression lexer
>
> tools/arch/arm64/include/asm/cputype.h | 8 +++++++-
> tools/arch/arm64/include/uapi/asm/kvm.h | 1 +
> tools/arch/x86/include/uapi/asm/kvm.h | 5 +++++
> tools/include/linux/build_bug.h | 9 +++++++++
> tools/include/uapi/linux/kvm.h | 3 +++
> tools/perf/tests/shell/buildid.sh | 15 ++++++++++++++-
> tools/perf/trace/beauty/include/linux/socket.h | 5 ++++-
> tools/perf/util/build-id.c | 10 +++++++---
> tools/perf/util/expr.l | 5 ++++-
> 9 files changed, 54 insertions(+), 7 deletions(-)
next prev parent reply other threads:[~2023-01-20 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:15 [GIT PULL] perf tools fixes for v6.2: 3rd batch Arnaldo Carvalho de Melo
2023-01-20 1:27 ` Arnaldo Carvalho de Melo [this message]
2023-01-20 18:46 ` pr-tracker-bot
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=Y8nuFmDDQU5c/4tS@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kcarcia@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=sohomdatta1+git@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=williams@redhat.com \
/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).