Messages in this thread |  | | Date | Tue, 16 Aug 2005 03:40:26 +0400 | From | "Vladimir B. Savkin" <> | Subject | idr_remove error with 2.6.13-rc6 |
| |
Hello! I saw the following in the logs: === START idr_remove called for id=200 which is not allocated.
Call Trace:<ffffffff8014abb0>{autoremove_wake_function+0} <ffffffff8023ee5f>{sub_remove+239} <ffffffff8023ee99>{idr_remove+41} <ffffffff802599b7>{release_dev+1815} <ffffffff801a1e42>{inotify_dentry_parent_queue_event+66} <ffffffff80191941>{dput+33} <ffffffff80259f41>{tty_release+17} <ffffffff8017a75a>{__fput+154} <ffffffff80178f3e>{filp_close+110} <ffffffff80136d53>{put_files_struct+115} <ffffffff80137ba9>{do_exit+489} <ffffffff80137f00>{sys_exit_group+0} <ffffffff801221c1>{ia32_sysret+0} === END AFAICT this caused no harm. The box is dual Opteron with 64-bit kernel and mixed userland. I saw a similar trace once with 2.6.13-rc5 too.
~ :wq With best regards, Vladimir Savkin.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |