From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.25.11-97.fc9 (P): idr_remove called for id=236 which is not allocated
Date: Fri, 15 Aug 2008 17:11:55 +0200 [thread overview]
Message-ID: <19f34abd0808150811w2b77479fnead3ae6b527ad4dc@mail.gmail.com> (raw)
Hi,
First the confessions: It's fedora-patched kernel, 2.6.25.11-97.fc9,
tainted by NVIDIA driver. So feel free to drop to /dev/null until I
can reproduce on a clean and recent kernel. (But -rc3 didn't boot for
me, and I don't have anything else handy atm.)
By bashing on random device nodes (with mknod + mmap as root), I got a
few messages of this kind:
idr_remove called for id=236 which is not allocated.
Pid: 3019, comm: a.out Tainted: P 2.6.25.11-97.fc9.i686 #1
[<c04f030c>] idr_remove+0xd5/0x138
[<c0540bfc>] release_dev+0x5bd/0x5cf
[<c04909fd>] ? d_free+0x3b/0x4d
[<c04955d0>] ? mntput_no_expire+0x16/0x69
[<c048309d>] ? __fput+0x149/0x151
[<c0540d8c>] tty_release+0x12/0x1c
[<c0483001>] __fput+0xad/0x151
[<c04830bc>] fput+0x17/0x19
[<c04807df>] filp_close+0x50/0x5a
[<c0480852>] sys_close+0x69/0xa1
[<c0405bf2>] syscall_call+0x7/0xb
[<c0620000>] ? agp_amd64_probe+0x134/0x3ee
=======================
idr_remove called for id=127 which is not allocated.
Pid: 3019, comm: a.out Tainted: P 2.6.25.11-97.fc9.i686 #1
[<c04f030c>] idr_remove+0xd5/0x138
[<c0540bfc>] release_dev+0x5bd/0x5cf
[<c04909fd>] ? d_free+0x3b/0x4d
[<c04955d0>] ? mntput_no_expire+0x16/0x69
[<c048309d>] ? __fput+0x149/0x151
[<c0540d8c>] tty_release+0x12/0x1c
[<c0483001>] __fput+0xad/0x151
[<c04830bc>] fput+0x17/0x19
[<c04807df>] filp_close+0x50/0x5a
[<c0480852>] sys_close+0x69/0xa1
[<c0405bf2>] syscall_call+0x7/0xb
=======================
It looks scary. Or is it purely my own fault?
Thanks,
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next reply other threads:[~2008-08-15 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 15:11 Vegard Nossum [this message]
2008-08-15 15:26 ` Alan Cox
2008-08-15 15:27 ` Vegard Nossum
2008-08-15 15:28 ` Alan Cox
2008-08-15 15:50 ` Vegard Nossum
2008-08-15 21:26 ` Vegard Nossum
2008-08-18 22:15 ` Alan Cox
2008-08-19 6:53 ` Vegard Nossum
2008-08-19 8:29 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0808150811w2b77479fnead3ae6b527ad4dc@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®