public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: shuah <shuah@kernel.org>, Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [GIT PULL] Kselftest fixes for Linux 6.13-rc3
Date: Wed, 11 Dec 2024 13:37:41 -0700	[thread overview]
Message-ID: <e3c2e67e-c80f-417c-a44f-e2f568e90d44@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

Hi Linus,

Please pull the following fixes update for Linux 6.13-rc3.

linux_kselftest-fixes-6.13-rc3

-- fixes the offset for kprobe syntax error test case when checking the
    BTF arguments on 64-bit powerpc.

Note: This fix has been in linux-next since last week. I had to drop
a patch and rebase this morning.

diff is attached.

thanks,
-- Shuah

----------------------------------------------------------------
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

   Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux_kselftest-fixes-6.13-rc3

for you to fetch changes up to 777f290ab328de333b85558bb6807a69a59b36ba:

   selftests/ftrace: adjust offset for kprobe syntax error test (2024-12-11 10:08:04 -0700)

----------------------------------------------------------------
linux_kselftest-fixes-6.13-rc3

-- fixes the offset for kprobe syntax error test case when checking the
    BTF arguments on 64-bit powerpc.

----------------------------------------------------------------
Hari Bathini (1):
       selftests/ftrace: adjust offset for kprobe syntax error test

  tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

----------------------------------------------------------------

[-- Attachment #2: linux_kselftest-fixes-6.13-rc3.diff --]
[-- Type: text/x-patch, Size: 805 bytes --]

diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc
index a16c6a6f6055..8f1c58f0c239 100644
--- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc
+++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc
@@ -111,7 +111,7 @@ check_error 'p vfs_read $arg* ^$arg*'		# DOUBLE_ARGS
 if !grep -q 'kernel return probes support:' README; then
 check_error 'r vfs_read ^$arg*'			# NOFENTRY_ARGS
 fi
-check_error 'p vfs_read+8 ^$arg*'		# NOFENTRY_ARGS
+check_error 'p vfs_read+20 ^$arg*'		# NOFENTRY_ARGS
 check_error 'p vfs_read ^hoge'			# NO_BTFARG
 check_error 'p kfree ^$arg10'			# NO_BTFARG (exceed the number of parameters)
 check_error 'r kfree ^$retval'			# NO_RETVAL

             reply	other threads:[~2024-12-11 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 20:37 Shuah Khan [this message]
2024-12-11 22:20 ` [GIT PULL] Kselftest fixes for Linux 6.13-rc3 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=e3c2e67e-c80f-417c-a44f-e2f568e90d44@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=torvalds@linux-foundation.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