From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965036AbVHOXkc (ORCPT ); Mon, 15 Aug 2005 19:40:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965035AbVHOXkc (ORCPT ); Mon, 15 Aug 2005 19:40:32 -0400 Received: from tentacle.s2s.msu.ru ([193.232.119.109]:47498 "EHLO tentacle.sectorb.msk.ru") by vger.kernel.org with ESMTP id S965036AbVHOXkc (ORCPT ); Mon, 15 Aug 2005 19:40:32 -0400 Date: Tue, 16 Aug 2005 03:40:26 +0400 From: "Vladimir B. Savkin" To: linux-kernel@vger.kernel.org Subject: idr_remove error with 2.6.13-rc6 Message-ID: <20050815234026.GA6036@tentacle.sectorb.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline X-Organization: Moscow State Univ., Institute of Mechanics X-Operating-System: Linux 2.6.11-ac7 User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello! I saw the following in the logs: === START idr_remove called for id=200 which is not allocated. Call Trace:{autoremove_wake_function+0} {sub_remove+239} {idr_remove+41} {release_dev+1815} {inotify_dentry_parent_queue_event+66} {dput+33} {tty_release+17} {__fput+154} {filp_close+110} {put_files_struct+115} {do_exit+489} {sys_exit_group+0} {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.