From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: BUG: using smp_processor_id() in preemptible
Date: Tue, 25 May 2010 08:57:42 +0300 [thread overview]
Message-ID: <1274767062.2106.6.camel@localhost> (raw)
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 (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: BUG: using smp_processor_id() in preemptible
Date: Tue, 25 May 2010 08:57:42 +0300 [thread overview]
Message-ID: <1274767062.2106.6.camel@localhost> (raw)
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
next reply other threads:[~2010-05-25 6:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 5:57 Artem Bityutskiy [this message]
2010-05-25 5:57 ` BUG: using smp_processor_id() in preemptible Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2018-01-11 12:31 Ricardo Nabinger Sanchez
2018-01-11 17:14 ` Eric Dumazet
2012-10-24 8:24 Paul Thompson
2012-10-24 22:39 ` Borislav Petkov
2009-06-24 14:15 Johannes Berg
2009-06-28 14:11 ` Avi Kivity
2009-06-29 8:32 ` Johannes Berg
2009-06-29 9:08 ` Avi Kivity
2009-06-29 9:54 ` Johannes Berg
2009-06-29 9:57 ` Johannes Berg
2009-06-29 10:00 ` Avi Kivity
2009-06-29 10:06 ` Johannes Berg
2009-06-29 10:16 ` Avi Kivity
2009-06-29 10:18 ` Johannes Berg
2009-06-29 10:25 ` Avi Kivity
2009-06-29 10:32 ` Johannes Berg
2009-06-29 10:39 ` Avi Kivity
2009-06-29 10:55 ` Johannes Berg
2009-06-29 11:38 ` Avi Kivity
2009-06-29 12:03 ` Johannes Berg
2009-06-29 9:59 ` Avi Kivity
2009-06-29 10:00 ` Johannes Berg
2009-06-29 10:04 ` Avi Kivity
2009-06-29 10:04 ` Johannes Berg
2008-12-08 12:13 Tim Blechmann
2009-01-13 9:44 ` Tim Blechmann
2009-02-20 20:42 ` Paul Gortmaker
2008-08-20 5:34 Aneesh Kumar K.V
2008-08-21 4:17 ` Eric Sandeen
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=1274767062.2106.6.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dmonakhov@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--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.