RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1490673 - Kernel Panic always happen immediately whenever make "debug.panic_on_rcu_stall=1" set on RHEL7.4
Summary: Kernel Panic always happen immediately whenever make "debug.panic_on_rcu_stal...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Qiao Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-12 01:56 UTC by Yasuhiro Ozone
Modified: 2020-12-14 09:59 UTC (History)
4 users (show)

Fixed In Version: kernel-3.10.0-720.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Kernel-3.10.0-693.el7 on RHEL7.4(GA) or later
Last Closed: 2018-04-10 22:02:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vmcore-dmesg.txt (36.98 KB, text/plain)
2017-09-12 02:03 UTC, Yasuhiro Ozone 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:1062 0 None None None 2018-04-10 22:04:24 UTC

Description Yasuhiro Ozone 2017-09-12 01:56:39 UTC 
Description of problem:
Kernel Panic always happen immediately whenever make "debug.panic_on_rcu_stall=1" set on RHEL7.4

Version-Release number of selected component (if applicable):

Kernel-3.10.0-693.el7 on RHEL7.4(GA) or later

How reproducible:

100%

Steps to Reproduce:
1.
# uname -r
3.10.0-693.1.1.el7.x86_64

2.
# cat /proc/sys/debug/panic_on_rcu_stall 
0

3.
# echo 1 > /proc/sys/debug/panic_on_rcu_stall

Actual results:

kernel panic always happen.

Expected results:

When set to 1, calls panic() after RCU stall detection messages

When 

Additional info:
Comment 2 Yasuhiro Ozone 2017-09-12 02:03:16 UTC 
Created attachment 1324651 [details]
vmcore-dmesg.txt
Comment 6 Pratyush Anand 2017-09-14 08:37:34 UTC 
It looks like RHEL commit 6cbfcf1526c74681ac81cda667f6f89016b47b8f backported upstream commit wrongly. We should have following diff on top of current RHEL7 code to backport upstream commit 088e9d253d3a4ab7e058dd84bb532c32dadf1882 correctly.

-------------------><--------------
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index f46e3e44c0af..981fb8baf895 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -1000,6 +1000,8 @@ static void print_cpu_stall(struct rcu_state *rsp)
                                     3 * rcu_jiffies_till_stall_check() + 3;
        raw_spin_unlock_irqrestore(&rnp->lock, flags);
 
+       panic_on_rcu_stall();
+
        set_need_resched();  /* kick ourselves to get things going. */
 }
 
@@ -1016,8 +1018,6 @@ static void check_cpu_stall(struct rcu_state *rsp, struct rcu_data *rdp)
                return;
        j = ACCESS_ONCE(jiffies);
 
-       panic_on_rcu_stall();
-
        /*
         * Lots of memory barriers to reject false positives.
         *
-------------------><--------------

I will prepare a brew build with above diff, I hope that should resolve it.
Comment 7 Yasuhiro Ozone 2017-09-22 02:25:31 UTC 
Hi all this is private account test.Please ignore it.
Comment 8 Rafael Aquini 2017-09-30 11:05:08 UTC 
Patch(es) committed on kernel repository and an interim kernel build is undergoing testing
Comment 10 Rafael Aquini 2017-10-02 14:22:23 UTC 
Patch(es) available on kernel-3.10.0-720.el7
Comment 14 errata-xmlrpc 2018-04-10 22:02:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:1062
Note You need to log in before you can comment on or make changes to this bug.