Fwd: Fw: [redhat-lspp] Unable to ssh in after certain system usage
Russell Coker
rcoker at redhat.com
Mon Mar 13 20:27:37 UTC 2006
On Thu, 2006-03-09 at 16:55 -0600, Michael Thompson wrote:
> > > Any idea where I should start?
> >
> > Looking in /var/log/messages, I get the following dump when I exit
> > from an ssh session:
> > idr_remove called for id=0 which is not allocated.
> > [<c01c4677>] idr_remove+0xd4/0x137
> > [<c0209fe4>] release_dev+0x632/0x649 [<c02e0f94>]
> > _spin_lock_irqsave+0x9/0xd
> > [<c0116b00>] __wake_up+0x2a/0x3d [<c0206e18>] tty_ldisc_deref+0x50/0x5f
> > [<c0176cea>] inotify_dentry_parent_queue_event+0x2b/0x90
> > [<c020a002>] tty_release+0x7/0xa
> > [<c0156664>] __fput+0xb1/0x14e [<c0154137>] filp_close+0x4e/0x54
> > [<c0102bc1>] syscall_call+0x7/0xb Mar 9 07:30:40 dyn94141107
> > kernel: [<c0102c52>] work_notifysig+0x13/0x19 idr_remove called
> > for id=0 which is not allocated.
> > Mar 9 07:30:40 dyn94141107 kernel: [<c01c4677>] idr_remove+0xd4/0x137
> > Mar 9 07:30:40 dyn94141107 kernel: [<c0209fe4>]
> > release_dev+0x632/0x649 [<c02e0f94>] _spin_lock_irqsave+0x9/0xd
> > Mar 9 07:30:40 dyn94141107 kernel: [<c0116b00>]
> > __wake_up+0x2a/0x3d [<c0206e18>] tty_ldisc_deref+0x50/0x5f
> > Mar 9 07:30:40 dyn94141107 kernel: [<c0176cea>]
> > inotify_dentry_parent_queue_event+0x2b/0x90 [<c020a002>]
> > tty_release+0x7/0xa
> > Mar 9 07:30:40 dyn94141107 kernel: [<c0156664>] __fput+0xb1/0x14e
> > [<c0154137>] filp_close+0x4e/0x54
> >
> > This happens every time I end an ssh session.
That is known as a symptom of a domain being permitted read or write
access to /dev/pts/X but not being permitted search access to /dev/pts.
This is considered a policy bug, I'll look for it later today.
More information about the redhat-lspp
mailing list