Bug 220726 - soft-safe -> soft-unsafe lock order detected (selinux/ssh)
Summary: soft-safe -> soft-unsafe lock order detected (selinux/ssh)
Keywords:
Status: CLOSED DUPLICATE of bug 220966
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Eric Paris
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-24 18:07 UTC by Ralf Ertzinger
Modified: 2007-11-30 22:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-01-09 14:39:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (9.01 KB, text/plain)
2006-12-24 18:07 UTC, Ralf Ertzinger
no flags Details
2905 /var/log/messages (67.29 KB, text/plain)
2007-01-08 16:51 UTC, dex
no flags Details
kernel panic on shutdown (1.18 MB, image/jpeg)
2007-01-08 16:59 UTC, dex
no flags Details
the other part of panic shot (1.24 MB, image/jpeg)
2007-01-08 17:02 UTC, dex
no flags Details

Description Ralf Ertzinger 2006-12-24 18:07:43 UTC
Description of problem:
ssh'ing into a machine running 2.6.19-1.2891.fc7 produces the log messages
attached to this bug.
selinux is configured as permissive,targetted

The ssh connection works afterwards.

Version-Release number of selected component (if applicable):
kernel-2.6.19-1.2891.fc7

How reproducible:
Always

Steps to Reproduce:
1. boot kernel
2. ssh into machine
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ralf Ertzinger 2006-12-24 18:07:43 UTC
Created attachment 144345 [details]
dmesg output

Comment 2 Deji Akingunola 2007-01-05 03:04:03 UTC
I'm seeing exactly the same message when I logged into 2.6.19-1.2904.fc7 on
x86_64, except its Xorg instead of ssh in dmesg output of comment#1. The system
still boot and logon on to the desktop though, only that usb drives don't
automount. Same usb drive automounts when booted into the 2.6.20rc3-rt kernel. 

Comment 3 dex 2007-01-08 16:51:45 UTC
Created attachment 145073 [details]
2905 /var/log/messages

2905 /var/log/messages

Comment 4 dex 2007-01-08 16:54:11 UTC
today I caught same error as comment #1 with sendmail can also confirm with ssh
also & kernel 2.6.19-1.2905.
also all kernels since 2.6.18-1.2849.fc6 crash on exit only got 2 screenshots no
logs may be related! full dmesg is included.
hardware: athlon-xp 2500 NVidia nforce2 chipset.  

Comment 5 dex 2007-01-08 16:59:15 UTC
Created attachment 145075 [details]
kernel panic on shutdown

Comment 6 dex 2007-01-08 17:02:23 UTC
Created attachment 145076 [details]
the other part of panic shot

Comment 7 Eric Paris 2007-01-09 14:39:34 UTC
dex, the 2 panics from comment 5 and 6 appear to be unrelated to this particular
issues.  would you mind filing them as a new BZ?

As for the issues discovered by the lock dependancy code in comments 1 and 3
this should be resolved upstream.  Until you get a fixed kernel it is possible
your machine will deadlock.  Test fedora kernels with a fix can be found at
http://people.redhat.com/eparis/BZ220966

I am going to mark this bug as a dup of 220966

*** This bug has been marked as a duplicate of 220966 ***

Comment 8 dex 2007-01-09 15:59:08 UTC
2.6.19-1.2906.fc7 sorted the panic on shutdown from #5 #6(whoohoo!)
testing kernel from comment #7 
2.6.19-1.2906.fc7 didnt help lock dependancy still there. watching & reporting @
#220966 now.


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