Linux Trace Kernel
 help / color / mirror / Atom feed
From: Tomas Glozar <tglozar@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Costa Shulyupin <costa.shul@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Tomas Glozar <tglozar@redhat.com>
Subject: [GIT PULL] RTLA additional fixes for v6.20
Date: Mon, 19 Jan 2026 14:50:38 +0100	[thread overview]
Message-ID: <20260119135038.756221-1-tglozar@redhat.com> (raw)

Steven,

please pull additional fixes for bugs that were caught in RTLA during
the testing of linux-next.

Thanks,
Tomas

The following changes since commit fb8b8183208d8efe824e8d2c73fb1ab5ad1191fd:

  rtla: Fix parse_cpu_set() return value documentation (2026-01-07 15:57:56 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tglozar/linux.git/ tags/rtla-v6.20-fixups

for you to fetch changes up to 6ea8a206108fe8b5940c2797afc54ae9f5a7bbdd:

  rtla: Fix parse_cpu_set() bug introduced by strtoi() (2026-01-13 08:32:52 +0100)

----------------------------------------------------------------
RTLA additional fixes for v6.20

- Fix bug in cpuset parsing

A commit queued for 6.20 changed atoi() to a new strtoi() function on
a tree-wide level. This broke cpuset parsing, which relies on atoi()'s
behavior of skipping non-numeric prefixes.

Revert cpuset parsing back to using atoi() to prevent the breakage.

The log entries above are purely informative; since the fix is for a bug
not yet merged upstream, it needs no mention in the merge description.

The tag was tested (make && make check) as well as pre-tested on top of
next-20260116. There are no additional known conflicts.

Signed-off-by: Tomas Glozar <tglozar@redhat.com>

----------------------------------------------------------------
Costa Shulyupin (1):
      rtla: Fix parse_cpu_set() bug introduced by strtoi()

 tools/tracing/rtla/src/utils.c | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)


                 reply	other threads:[~2026-01-19 13:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260119135038.756221-1-tglozar@redhat.com \
    --to=tglozar@redhat.com \
    --cc=costa.shul@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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