From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: 2.6.12-mm1: BUG() in fd_install, RCU related?
Date: Tue, 21 Jun 2005 10:34:24 +0200 [thread overview]
Message-ID: <20050621083424.GA2076@elf.ucw.cz> (raw)
Hi!
I got
Jun 21 10:30:20 amd kernel: ------------[ cut here ]------------
Jun 21 10:30:20 amd kernel: kernel BUG at fs/open.c:935!
Jun 21 10:30:20 amd kernel: invalid operand: 0000 [#1]
Jun 21 10:30:20 amd kernel: Modules linked in: ipw2100
Jun 21 10:30:20 amd kernel: CPU: 0
Jun 21 10:30:20 amd kernel: EIP: 0060:[page_referenced+39/160] Not tainted VLI
Jun 21 10:30:20 amd kernel: EFLAGS: 00010286 (2.6.12-mm1)
Jun 21 10:30:20 amd kernel: EIP is at fd_install+0x27/0x40
Jun 21 10:30:20 amd kernel: eax: f7268e00 ebx: 00000080 ecx: f61a9800 edx: f6106400
Jun 21 10:30:20 amd kernel: esi: f6106400 edi: f61a9800 ebp: 0000000c esp: f66d9f7c
Jun 21 10:30:20 amd kernel: ds: 007b es: 007b ss: 0068
Jun 21 10:30:20 amd kernel: Process kded (pid: 2056, threadinfo=f66d8000 task=f672ca80)
Jun 21 10:30:20 amd kernel: Stack: 00000080 c0165fd6 00000080 ffffffea 0000000c c0166300 00000000 f6106400
Jun 21 10:30:20 amd kernel: fffffff7 c01664b0 f6106400 0000000c 00000080 b6e84b7c f66d8000 c0102ea9
Jun 21 10:30:20 amd kernel: 0000000c 00000000 00000080 00000080 b6e84b7c bf9361f8 000000dd 0000007b
Jun 21 10:30:20 amd kernel: Call Trace:
Jun 21 10:30:20 amd kernel: [blkdev_get+38/160] dupfd+0x46/0x60
Jun 21 10:30:20 amd kernel: [lookup_bdev+48/144] do_fcntl+0x80/0x150
Jun 21 10:30:20 amd kernel: [.text.lock.block_dev+153/185] sys_fcntl64+0x80/0x90
Jun 21 10:30:20 amd kernel: [do_signal+57/288] syscall_call+0x7/0xb
Jun 21 10:30:20 amd kernel: Code: 00 00 00 00 53 89 c3 b8 00 e0 ff ff 21 e0 8b 00 8b 80 54 04 00 00 8b 48 04 8b 41 0c 8b 04 98 85 c0 75 08 8b 41 0c 89 14 98 5b c3 <0f> 0b a7 03 3c be 52 c0 eb ee eb 0d 90 90 90 90 90 90 90 90 90
Jun 21 10:31:54 amd pam_limits[1559]: wrong limit value 'unlimited'
..while doing nothing particulary interesting. Its:
void fastcall fd_install(unsigned int fd, struct file * file)
{
struct files_struct *files = current->files;
struct fdtable *fdt;
spin_lock(&files->file_lock);
fdt = files_fdtable(files);
if (unlikely(fdt->fd[fd] != NULL))
BUG();
~~~~~~~~~~~~~~~~~~~~~~
rcu_assign_pointer(fdt->fd[fd], file);
spin_unlock(&files->file_lock);
}
This bug. (Is there any particular reason why the code does not use
BUG_ON())?
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
next reply other threads:[~2005-06-21 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 8:34 Pavel Machek [this message]
2005-06-21 9:07 ` 2.6.12-mm1: BUG() in fd_install, RCU related? Dipankar Sarma
2005-06-21 9:15 ` Pavel Machek
2005-06-23 11:50 ` syrius.ml
2005-06-23 19:02 ` Dipankar Sarma
2005-06-23 21:47 ` Rafael J. Wysocki
2005-06-23 23:05 ` syrius.ml
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=20050621083424.GA2076@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--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