* BUG: using smp_processor_id() in preemptible
@ 2010-05-25 5:57 Artem Bityutskiy
0 siblings, 0 replies; only message in thread
From: Artem Bityutskiy @ 2010-05-25 5:57 UTC (permalink / raw)
To: Dmitry Monakhov; +Cc: linux-fsdevel, LKML
Hi,
I get tons of these debugging complaints with the latest Linus' tree:
BUG: using smp_processor_id() in preemptible [00000000] code: sync/2503
caller is dqstats_inc+0x19/0x2c
Pid: 2503, comm: sync Tainted: G D 2.6.34-misc-2.6 #9
Call Trace:
[<ffffffff811ad1a2>] debug_smp_processor_id+0xc2/0xdc
[<ffffffff81134c7e>] dqstats_inc+0x19/0x2c
[<ffffffff8113786e>] vfs_quota_sync+0x1bd/0x2a5
[<ffffffff8111252b>] ? sync_one_sb+0x0/0x1d
[<ffffffff811124e7>] __sync_filesystem+0x3a/0x7e
[<ffffffff81112546>] sync_one_sb+0x1b/0x1d
[<ffffffff810f4d70>] iterate_supers+0x6d/0xb2
[<ffffffff81112477>] sync_filesystems+0x1b/0x1d
[<ffffffff81112564>] sys_sync+0x1c/0x2e
[<ffffffff81002a6b>] system_call_fastpath+0x16/0x1b
and git blame points to you.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-05-25 6:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-25 5:57 BUG: using smp_processor_id() in preemptible Artem Bityutskiy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).