Bug 455337 - 2.6.26-136.fc10.i686: INFO: hard-read-safe -> hard-read-unsafe lock order detected
2.6.26-136.fc10.i686: INFO: hard-read-safe -> hard-read-unsafe lock order det...
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-14 17:11 EDT by Tom London
Modified: 2008-10-10 00:18 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-10 00:18:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Complete INFO spew (235.87 KB, text/plain)
2008-07-14 17:11 EDT, Tom London
no flags Details

  None (edit)
Description Tom London 2008-07-14 17:11:59 EDT
Description of problem:
Got the following INFO in /var/log/messages (complete spew attached below):


======================================================
[ INFO: hard-read-safe -> hard-read-unsafe lock order detected ]
2.6.26-136.fc10.i686 #1
------------------------------------------------------
strace/4454 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
 (&utrace->lock){--..}, at: [<c045b904>] get_utrace_lock_attached+0x4a/0x8d

and this task is already holding:
 (tasklist_lock){..??}, at: [<c042db06>] do_exit+0x2f3/0x784
which would create a new lock dependency:
 (tasklist_lock){..??} -> (&utrace->lock){--..}


Version-Release number of selected component (if applicable):
kernel-2.6.26-136.fc10.i686

How reproducible:
Don't know

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Tom London 2008-07-14 17:11:59 EDT
Created attachment 311778 [details]
Complete INFO spew
Comment 2 Tom London 2008-07-14 17:14:16 EDT
Not 100% sure, but I think I was doing "strace ping www.comcast.net".

That fails when run as a "ordinary" user, but succeeds if run as root.
Comment 3 Tom London 2008-10-06 12:02:41 EDT
Haven't seen this for quite some time.

Close?

Note You need to log in before you can comment on or make changes to this bug.