linux-kernel - lockup in rb_get_reader

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: <m2u5df78e1d1003301627ya1f621f7qaf0ad099f62d787e@mail.gmail.com>
Date:	Tue, 30 Mar 2010 16:27:49 -0700
From:	Jiaying Zhang <jiayingz@...gle.com>
To:	Steven Rostedt <srostedt@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Michael Rubin <mrubin@...gle.com>,
	David Sharp <dhsharp@...gle.com>, linux-kernel@...r.kernel.org
Subject: lockup in rb_get_reader_page

Hi Steven,

We recently saw some cpu lockups while running kernel tracing.
The problem started to happen after we synced up our ring buffer
code with the upstream lockless ring buffer change. It usually
took many hours and heavy trace load to hit this problem. When
the lockup happens, the problematic cpu seemed to be in an infinite
loop of trying to grab the head_page in rb_get_reader_page().

We would like to check with you on whether this is a known issue.
If so, do we have a bug fix? If not, do you have any suggestions on
where we should check?

Thanks a lot!

Jiaying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/