lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f32a8e2-7fc3-427b-b1e2-238fe81ce97e@paulmck-laptop>
Date:   Tue, 28 Mar 2023 10:48:14 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     torvalds@...ux-foundation.org
Cc:     mingo@...nel.org, linux-kernel@...r.kernel.org,
        douglas.raillard@....com, tglx@...utronix.de, rcu@...r.kernel.org,
        kernel-team@...com, rostedt@...dmis.org
Subject: [GIT PULL] Fix rcu_torture_read ftrace event

Hello, Linus,

This post-merge-window urgent pull request brings the rcu_torture_read
event trace into line with the new trace tools.  Without this commit,
users of those tools perceive a regression.

Just in case there is confusion, the plan is still for Joel Fernandes
and Boqun Feng to send the RCU pull request into the v6.4 merge window.
I will be doing my other pull requests for v6.4, and I will also be
handling the RCU pull request for the v6.5 merge window.

The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:

  Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/urgent-rcu.2023.03.28a

for you to fetch changes up to d18a04157fc171fd48075e3dc96471bd3b87f0dd:

  rcu: Fix rcu_torture_read ftrace event (2023-03-22 14:05:24 -0700)

----------------------------------------------------------------
Urgent RCU pull request for v6.3

This commit brings the rcu_torture_read event trace into line with
the new trace tools by replacing this event trace's __field() with the
corresponding __array().  Without this commit, the new trace tools will
fail when presented wtih an rcu_torture_read event trace, which is a
regression from the viewpoint of trace tools users.

https://lore.kernel.org/all/20230320133650.5388a05e@gandalf.local.home/

----------------------------------------------------------------
Douglas Raillard (1):
      rcu: Fix rcu_torture_read ftrace event

 include/trace/events/rcu.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ