From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Preempt & Xfs Question
Date: Thu, 27 Jan 2005 16:18:56 +0000 [thread overview]
Message-ID: <41F91470.6040204@tiscali.de> (raw)
Hi!
I have a question: Why do I get such debug messages:
BUG: using smp_processor_id() in preemptible [00000001] code: khelper/892
caller is _pagebuf_lookup_pages+0x11b/0x362
[<c03119c7>] smp_processor_id+0xa3/0xb4
[<c02ef802>] _pagebuf_lookup_pages+0x11b/0x362
[<c02ef802>] _pagebuf_lookup_pages+0x11b/0x362
[<c02efe31>] xfs_buf_get_flags+0x106/0x141
[<c02efeaa>] xfs_buf_read_flags+0x3e/0xae
[<c02e0fd5>] xfs_trans_read_buf+0x18b/0x389
[<c02ada32>] xfs_da_do_buf+0x735/0x88c
[<c0127f46>] run_timer_softirq+0x12d/0x1c7
[<c02adc1b>] xfs_da_read_buf+0x47/0x4b
[<c02b1b22>] xfs_dir2_block_lookup_int+0x52/0x1b4
[<c02b1b22>] xfs_dir2_block_lookup_int+0x52/0x1b4
[<c011f189>] vprintk+0x133/0x16a
[<c0101319>] kernel_thread_helper+0x5/0xb
[<c0130253>] __kernel_text_address+0x28/0x36
[<c02b1a10>] xfs_dir2_block_lookup+0x2f/0xef
[<c02b0967>] xfs_dir2_isblock+0x2c/0x74
[<c02aff4e>] xfs_dir2_lookup+0x176/0x186
[<c01389d9>] __print_symbol+0x86/0xef
[<c02e214e>] xfs_dir_lookup_int+0x4c/0x144
[<c04cf6aa>] _spin_lock+0x16/0x7c
[<c02e7cc8>] xfs_lookup+0x55/0x8a
[<c02f4736>] linvfs_lookup+0x52/0x99
[<c01698a2>] real_lookup+0xc2/0xe3
[<c0169b2c>] do_lookup+0x96/0xa1
[<c0169cd0>] link_path_walk+0x199/0xe3a
[<c012a2f1>] do_notify_parent+0x108/0x214
[<c016ac39>] path_lookup+0x97/0x15f
[<c0166612>] open_exec+0x2f/0x102
[<c011834b>] task_rq_lock+0x36/0x66
[<c01676ed>] do_execve+0x42/0x201
[<c0101cc1>] sys_execve+0x46/0x9c
[<c010318b>] syscall_call+0x7/0xb
[<c012e60e>] ____call_usermodehelper+0xa1/0xc0
[<c012e56d>] ____call_usermodehelper+0x0/0xc0
[<c0101319>] kernel_thread_helper+0x5/0xb
Does the XFS Module avoid preemption rules? If so, why?
Thanks
Matthias-Christian Ott
--
http://unixforge.org/~matthias-christian-ott/
next reply other threads:[~2005-01-27 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 16:18 Matthias-Christian Ott [this message]
2005-01-27 15:29 ` Preempt & Xfs Question Steve Lord
2005-01-27 15:40 ` Chris Wedgwood
2005-01-27 17:46 ` Matthias-Christian Ott
2005-01-27 15:53 ` Chris Wedgwood
2005-01-27 18:24 ` Matthias-Christian Ott
2005-01-27 16:51 ` Chris Wedgwood
2005-01-27 19:24 ` Matthias-Christian Ott
2005-01-27 21:11 ` Nathan Scott
2005-01-27 17:41 ` Matthias-Christian Ott
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=41F91470.6040204@tiscali.de \
--to=matthias.christian@tiscali.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.