Description of problem: Saw an error show up in the dmesg log after I had been doing some strace runs on various processes. Version-Release number of selected component (if applicable): 2.6.18-8.1.3.el5 How reproducible: Unknown Steps to Reproduce: 1. Strace a process (unsure of the circumstances) 2. 3. Actual results: Saw this kernel error in dmesg: idr_remove called for id=0 which is not allocated. Call Trace: [<ffffffff8013b97d>] idr_remove+0xe0/0x14d [<ffffffff8018698d>] release_dev+0x65d/0x67b [<ffffffff80051314>] tty_release+0x11/0x1a [<ffffffff80012281>] __fput+0xae/0x198 [<ffffffff80023647>] filp_close+0x5c/0x64 [<ffffffff8001d5cd>] sys_close+0x88/0xa2 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc Expected results: No error Additional info:
I believe this is one of the possible symptoms of the bug in init_dev() that was fixed in 2.6.18-19.el5 with the following patch tracking file: pty-fix-race-that-could-lead-to-double-idr-index-free.patch If the problem still occurs with the current RHEL5.1 beta kernel, please reopen this bug report. Note to DonZ: that patch tracking file should list bug 230500 in the header (instead of RHEL4 bug 214188). *** This bug has been marked as a duplicate of 230500 ***