ee43e564223f195...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in preemptible [] code:
syz-executor.0/15841
caller is debug_smp_processor_id+0x20/0x24 lib/smp_processor_id.c:64
CPU: 0 PID: 15841 Comm: syz-executor.0 Not tainted 5.12.0-rc2-syzkaller #0
Hardware name: ARM-Versatile Express
Backtra
syzbot suspects this issue was fixed by commit:
commit bb8872a1e6bc911869a729240781076ed950764b
Author: Tuong Lien
Date: Sat Aug 29 19:37:55 2020 +
tipc: fix using smp_processor_id() in preemptible
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100f5bb850
start commi
syzbot has bisected this issue to:
commit e1f32190cf7ddd55778b460e7d44af3f76529698
Author: Tuong Lien
Date: Fri Nov 8 05:05:12 2019 +
tipc: add support for AEAD key setting via netlink
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11b738a090
start commit: 11ba4688
rc 1!
BUG: using smp_processor_id() in preemptible [] code:
syz-executor201/6801
caller is tipc_aead_tfm_next net/tipc/crypto.c:402 [inline]
caller is tipc_aead_encrypt net/tipc/crypto.c:639 [inline]
caller is tipc_crypto_xmit+0x80a/0x2790 net/tipc/crypto.c:1605
CPU: 0 PID: 6801 Comm: syz-e
c09b2...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in preemptible [] code:
syz-executor.1/23385
caller is tipc_aead_tfm_next net/tipc/crypto.c:402 [inline]
caller is tipc_aead_encrypt net/tipc/crypto.c:639 [inline]
caller is tipc_crypto_xmit+0x80a/0x2790 net/tipc/crypto.c:1605
CPU:
On Fri, Jun 12, 2020 at 10:20:35PM +0530, Ritesh Harjani wrote:
> > I am seeing this all over the place on Linus's tree right now:
> >
> > [ +0.008563] BUG: using smp_processor_id() in preemptible [] code:
> > systemd/1
> > [ +0.11] calle
aceda0
RBP: 01ed R08: feff R09: 004c
R10: 5637eeaced80 R11: 0246 R12: 0012
R13: 5637eeacf640 R14: R15: 00000000
BUG: using smp_processor_id() in preemptible [] code:
systemd-tmpfile/3971
cal
92adf6f8b4
dashboard link: https://syzkaller.appspot.com/bug?extid=38af52cdcc116cee7742
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38af52cdcc116cee7...@syzkaller.appspotmail.com
BUG: using smp_pr
/0x16a0 kernel/workqueue.c:2269
worker_thread+0x96/0xe10 kernel/workqueue.c:2415
kthread+0x388/0x470 kernel/kthread.c:268
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:351
BUG: using smp_processor_id() in preemptible [] code: kworker/u4:1/21
caller is ext4_mb_new_blocks+0xa77/0x3b30 fs
I am seeing this all over the place on Linus's tree right now:
[ +0.008563] BUG: using smp_processor_id() in preemptible [] code:
systemd/1
[ +0.11] caller is ext4_mb_new_blocks+0x2ac/0xc10
[ +0.02] CPU: 31 PID: 1 Comm: systemd Not tainted
5.7.0-14371-g25ae6195a4c
On Fri, Jun 12, 2020 at 07:09:04PM +0530, Ritesh Harjani wrote:
> I see Ted has already taken v2 of this patch in his dev repo.
> Should be able to see in linux tree soon.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?h=dev&id=811985365378df01386c3cfb7ff716e74ca376d5
re
about discard_pa_seq only when the block allocation fails and then too
we add the seq counter of all the cpus against the initial sampled one
to check if anyone has freed any blocks while we were doing allocation.
So just use raw_cpu_ptr to not trigger this BUG.
BUG: using smp_processor_id() in pre
we care
> about discard_pa_seq only when the block allocation fails and then too
> we add the seq counter of all the cpus against the initial sampled one
> to check if anyone has freed any blocks while we were doing allocation.
>
> So just use raw_cpu_ptr to not trigger this BUG.
>
the following tag to the commit:
> Reported-by: syzbot+0113b9be6667b5b50...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> systemd-rfkill/6740
> caller is ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 6740 Com
68.080829][ T6736] BUG: using
smp_processor_id() in preemptible [] code: systemd-rfkill/6736
e UTMP about Sys[ 68.090431][ T6736] caller is
ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711
tem Runlevel Cha[ 68.098400][ T6736] CPU: 0 PID: 6736 Comm: systemd-rfkill
Not tainted 5.7.0
BUG: using smp_processor_id() in preemptible [] code:
systemd-rfkill/6724
caller is ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711
CPU: 0 PID: 6724 Comm: systemd-rfkill Not tainted 5.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
01/01/2011
BUG: using smp_processor_id() in preemptible [] code:
systemd-rfkill/6740
caller is ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711
CPU: 0 PID: 6740 Comm: systemd-rfkill Not tainted 5.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
01/01/2011
following tag to the commit:
> Reported-by: syzbot+c2a0ce95f0c47bcd4...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> systemd-rfkill/6910
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 6910 Comm: sy
following tag to the commit:
> Reported-by: syzbot+ca020d38a27ddc8e3...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code: kworker/u4:4/198
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 198 Comm: kworke
following tag to the commit:
> Reported-by: syzbot+f72682b02970a74a7...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> systemd-rfkill/6769
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 6769 Comm: sy
following tag to the commit:
> Reported-by: syzbot+878f276b4892a4438...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code: syz-fuzzer/6793
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 6793 Comm: syz-fuzzer N
following tag to the commit:
> Reported-by: syzbot+5c2f1b4ae8c49a698...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> kworker/u4:5/4205
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 4205 Comm: kwo
following tag to the commit:
> Reported-by: syzbot+9ce464e21fc2ab95d...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 41 Comm: kworker/u4:2 N
link: https://syzkaller.appspot.com/bug?extid=f72682b02970a74a7858
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+f72682b02970a74a7...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
process_one_work+0x965/0x1690 kernel/workqueue.c:2269
worker_thread+0x96/0xe10 kernel/workqueue.c:2415
kthread+0x3b5/0x4a0 kernel/kthread.c:291
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
BUG: using smp_processor_id() in preemptible [] code: kworker/u4:5/4205
caller is
]
wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
process_one_work+0x965/0x1690 kernel/workqueue.c:2269
worker_thread+0x96/0xe10 kernel/workqueue.c:2415
kthread+0x3b5/0x4a0 kernel/kthread.c:291
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
BUG: using smp_processor_id() in preemptible [
link: https://syzkaller.appspot.com/bug?extid=878f276b4892a4438f95
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+878f276b4892a4438...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=c2a0ce95f0c47bcd4b37
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+c2a0ce95f0c47bcd4...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=ca020d38a27ddc8e3cae
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ca020d38a27ddc8e3...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
On Fri, Jun 05, 2020 at 04:29:22AM -0700, Matthew Wilcox wrote:
> On Thu, Jun 04, 2020 at 08:55:55PM -0700, Eric Biggers wrote:
> > Possibly a bug in lib/radix-tree.c? this_cpu_ptr() in
> > radix_tree_node_alloc()
> > can be reached without a prior preempt_disable(). Or is the caller of
> > idr_
003
> > RBP: 0005 R08: 0001 R09: 00000031
> > R10: R11: 0246 R12: 00401f50
> > R13: 00401fe0 R14: R15:
> > BUG: using smp_processor_id() in preemptible [0
syzbot has bisected this bug to:
commit e42671084361302141a09284fde9bbc14fdd16bf
Author: Manivannan Sadhasivam
Date: Thu May 7 12:53:06 2020 +
net: qrtr: Do not depend on ARCH_QCOM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e2221210
start commit: acf25aa6 Mer
ing tag to the commit:
> Reported-by: syzbot+8ea916061cc749544...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> kworker/u4:6/6740
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 6740 Comm: kworker/u4:6 Not
ing tag to the commit:
> Reported-by: syzbot+7f2b4a7d4281e8c2a...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> systemd-rfkill/6731
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 6731 Comm: systemd-
ing tag to the commit:
> Reported-by: syzbot+cd8a20b91d68ef113...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code: syz-fuzzer/6927
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 6927 Comm: syz-fuzzer Not taint
ing tag to the commit:
> Reported-by: syzbot+94f7894cc5600cc07...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code:
> systemd-rfkill/6726
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 6726 Comm: systemd-
C
> handling
>
Hmm, syzbot reported this several times already. Marking it as a duplicate
of the report where the discussion happened:
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
- Eric
ing tag to the commit:
> Reported-by: syzbot+4d28f1825b8fb92fa...@syzkaller.appspotmail.com
>
> BUG: using smp_processor_id() in preemptible [] code: kworker/u4:3/46
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 46 Comm: kworker/u4:3 Not taint
0006cb018 R08: 0001 R09: 004002c8
> R10: R11: 000000000246 R12: 00401e90
> R13: 00401f20 R14: R15:
> BUG: using smp_processor_id() in preemptible [] code:
> syz-executor013/7182
> caller is radix_t
> dashboard link: https://syzkaller.appspot.com/bug?extid=aed048f49c59eb997737
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+aed048f49c59eb997...@syzkaller.appspotmail.co
: 0003
> RBP: 0005 R08: 0001 R09: 0031
> R10: R11: 0246 R12: 00401f50
> R13: 00401fe0 R14: 0000 R15:
> BUG: using smp_processor_id() in preemptible [] code:
01 R09: 0031
R10: R11: 0246 R12: 00401f50
R13: 00401fe0 R14: R15: 00000000
BUG: using smp_processor_id() in preemptible [] code:
syz-executor036/6796
caller is radix_tree_node_alloc.constprop.0+0x200
link: https://syzkaller.appspot.com/bug?extid=aed048f49c59eb997737
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+aed048f49c59eb997...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
uot;)
RDX: RSI: 2100 RDI: 0004
RBP: 006cb018 R08: 0001 R09: 004002c8
R10: R11: 0246 R12: 00401e90
R13: 00401f20 R14: R15: 00000000
BUG: using smp_processor_id() in p
+82f324bb69744c5f6...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in preemptible [] code: syz-fuzzer/6792
caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
Fix 42f56b7a4a7d ("ext4: mballoc: introduce pcpu seqcnt for freeing PA
to improve ENOSPC handling") by
against the initial sampled one
to check if anyone has freed any blocks while we were doing allocation.
So just use raw_cpu_ptr to not trigger this BUG.
BUG: using smp_processor_id() in preemptible [] code: syz-fuzzer/6927
caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
CP
> #syz test:
This crash does not have a reproducer. I cannot test it.
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 0e21d4620dd047da7952f44a2e1ac777ded2d57e
link: https://syzkaller.appspot.com/bug?extid=7f2b4a7d4281e8c2aad0
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7f2b4a7d4281e8c2a...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=8ea916061cc749544c8f
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+8ea916061cc749544...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=94f7894cc5600cc07094
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+94f7894cc5600cc07...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=4d28f1825b8fb92fa383
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4d28f1825b8fb92fa...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=82f324bb69744c5f6969
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+82f324bb69744c5f6...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
link: https://syzkaller.appspot.com/bug?extid=cd8a20b91d68ef113b45
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+cd8a20b91d68ef113...@syzkaller.appspotmail.com
BUG: using smp_processor_id() in
rted-by: syzbot+55acd54b57bb4b384...@syzkaller.appspotmail.com
Started in network mode
Own node identity ff030001, cluster identity 4711
BUG: using smp_processor_id() in preemptible [] code:
mime_typevmnet0/24282
caller is dst_cache_get+0x3d/0xb0 net/core/dst_cache.c:68
CP
Started in network mode
Own node identity 7f01, cluster identity 4711
New replicast peer: 172.20.20.22
check_preemption_disabled: 3 callbacks suppressed
BUG: using smp_processor_id() in preemptible [] code:
syz-executor834/8612
caller is dst_cache_get+0x3d/0xb0 net/core/dst_cache.c:68
On Sun, Jan 07, 2018 at 09:53:19AM +0100, Thomas Zeitlhofer wrote:
> On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote:
> > On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote:
[...]
> > > While solving the previous problem, this patch also introduces new
> > > "fun a
gt; > > > On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > > > > Yes:
> > > > > >
> > > > > >BUG: using smp_processor_id() in preemptible [] code:
> > > > > > ovsdb-server/4498
> &g
ote:
> > > > > Yes:
> > > > >
> > > > >BUG: using smp_processor_id() in preemptible [] code:
> > > > > ovsdb-server/4498
> > > > >caller is native_flush_tlb_single+0x57/0xc0
> > > > >CPU: 2 PID: 449
On Thu, Jan 04, 2018 at 07:38:00PM +0100, Thomas Zeitlhofer wrote:
> On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> > On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > > Yes:
> > > >
> > > > BUG: using smp_
On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > Yes:
> > >
> > > BUG: using smp_processor_id() in preemptible [] code:
> > > ovsdb-server/4498
> > >
On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > Yes:
> >
> >BUG: using smp_processor_id() in preemptible [] code:
> > ovsdb-server/4498
> >caller is native_flush_tlb_single+0x57/0xc0
> >CPU: 2 PID: 4498 Comm: ovsdb-se
On Thu, 4 Jan 2018, Thomas Zeitlhofer wrote:
> On Thu, Jan 04, 2018 at 01:55:28PM +0100, Greg Kroah-Hartman wrote:
> > > > > > on an Ivybridge CPU, I get with 4.14.11:
> > > > > >
> > > > > >BUG: using smp_processor_id() in pr
te:
> > > > On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> > > > > Hello,
> > > > >
> > > > > on an Ivybridge CPU, I get with 4.14.11:
> > > > >
> > > > >BUG: using smp_processor_id() in
ote:
> > > > Hello,
> > > >
> > > > on an Ivybridge CPU, I get with 4.14.11:
> > > >
> > > >BUG: using smp_processor_id() in preemptible [] code:
> > > > ovsdb-server/4510
> > > >caller is native_flus
As I see the error message only on Ivybridge and not on Haswell, I came
up with the vague guess that this could be related.
> The 4.4 and 4.9 backports are much different than the 4.14 tree.
Yes, I have seen that.
> > JFYI, the very same kernel does not show this issue
On Thu, Jan 04, 2018 at 11:20:29AM +0100, Thomas Zeitlhofer wrote:
> On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> > Hello,
> >
> > on an Ivybridge CPU, I get with 4.14.11:
> >
> > BUG: using smp_processor_id() in preemptible [0
On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> Hello,
>
> on an Ivybridge CPU, I get with 4.14.11:
>
>BUG: using smp_processor_id() in preemptible [] code:
> ovsdb-server/4510
>caller is native_flush_tlb_single+0x57/0xc0
>CPU:
Hello,
on an Ivybridge CPU, I get with 4.14.11:
BUG: using smp_processor_id() in preemptible [] code:
ovsdb-server/4510
caller is native_flush_tlb_single+0x57/0xc0
CPU: 3 PID: 4510 Comm: ovsdb-server Not tainted
4.14.11-kvm-00434-gcd0b8eb84f5c #3
Hardware name: MSI MS-7798
On Fri 09-12-16 15:28:20, Michal Hocko wrote:
> Hi Andy,
> I am hitting the following
> [ 570.715345] BUG: using smp_processor_id() in preemptible [] code:
> umount/6193
> [ 570.716880] caller is debug_smp_processor_id+0x17/0x19
> [ 570.717876] CPU: 2 PID: 6193 Comm:
Hi Andy,
I am hitting the following
[ 570.715345] BUG: using smp_processor_id() in preemptible [] code:
umount/6193
[ 570.716880] caller is debug_smp_processor_id+0x17/0x19
[ 570.717876] CPU: 2 PID: 6193 Comm: umount Tainted: GW
4.9.0-rc8-nofstest4-next-20161209-00012
Benjamin Block wrote:
> >>>>>>
> >>>>>>>Hej Mike,
> >>>>>>>
> >>>>>>>when running a debug-kernel today with several multipath-devices using
> >>>>>>>the round-robin path selector I notice
l multipath-devices using
> > >>>>the round-robin path selector I noticed that the kernel throws these
> > >>>>warnings here:
> > >>>>
> > >>>>BUG: using smp_processor_id() in preemptible [] code:
> > >>>&g
wrote:
On Wed, Aug 03 2016 at 11:35am -0400,
Benjamin Block wrote:
Hej Mike,
when running a debug-kernel today with several multipath-devices using
the round-robin path selector I noticed that the kernel throws these
warnings here:
BUG: using smp_processor_id() in preemptible [] code
Thanks Xiaolong, I will prepare a fix.
dr
policy to enable vm86 if you are using a vm86-based DOS emulator.
[ 33.211822] BUG: using smp_processor_id() in preemptible [] code:
trinity-c0/632
[ 33.211822] BUG: using smp_processor_id() in preemptible [] code:
trinity-c0/632
[ 33.213901] caller is debug_smp_process
l multipath-devices using
> > >>>>the round-robin path selector I noticed that the kernel throws these
> > >>>>warnings here:
> > >>>>
> > >>>>BUG: using smp_processor_id() in preemptible [] code:
> > >>>&g
,
Benjamin Block wrote:
Hej Mike,
when running a debug-kernel today with several multipath-devices using
the round-robin path selector I noticed that the kernel throws these
warnings here:
BUG: using smp_processor_id() in preemptible [] code: kdmwork-252:0/881
caller is rr_select_path+0x36/0x108
11:35am -0400,
> >>>Benjamin Block wrote:
> >>>
> >>>>Hej Mike,
> >>>>
> >>>>when running a debug-kernel today with several multipath-devices using
> >>>>the round-robin path selector I noticed that the kernel throws
round-robin path selector I noticed that the kernel throws these
warnings here:
BUG: using smp_processor_id() in preemptible [] code: kdmwork-252:0/881
caller is rr_select_path+0x36/0x108 [dm_round_robin]
CPU: 1 PID: 881 Comm: kdmwork-252:0 Not tainted 4.7.0-debug #4
617679b8
multipath-devices using
> >>the round-robin path selector I noticed that the kernel throws these
> >>warnings here:
> >>
> >>BUG: using smp_processor_id() in preemptible [] code:
> >>kdmwork-252:0/881
> >>caller is rr_sele
smp_processor_id() in preemptible [] code: kdmwork-252:0/881
caller is rr_select_path+0x36/0x108 [dm_round_robin]
CPU: 1 PID: 881 Comm: kdmwork-252:0 Not tainted 4.7.0-debug #4
617679b8 61767a48 0002
61767ae8 61767a60
On Wed, Aug 03 2016 at 11:35am -0400,
Benjamin Block wrote:
> Hej Mike,
>
> when running a debug-kernel today with several multipath-devices using
> the round-robin path selector I noticed that the kernel throws these
> warnings here:
>
> BUG: using smp_processor_id() in
Hi,
We're using your driver on a HP ProLiant DL360 Gen9, but we keep getting
flooded with the following BUG.
BUG: using smp_processor_id() in preemptible [] code: splice-io/6/3248
caller is debug_smp_processor_id+0x17/0x1c
CPU: 4 PID: 3248 Comm: splice-io/6 Not tainted 4.4.8-
0] Freeing unused kernel memory: 1252K (8800018c7000 -
880001a0)
[3.432811] Freeing unused kernel memory: 664K (880001d5a000 -
880001e0)
[3.434324] BUG: using smp_processor_id() in preemptible [] code:
swapper/0/1
[3.435848] caller is debug_smp_process
el memory: 464K (cafc4000 - cb038000)
[1.260249] Write protecting the kernel text: 3276k
[1.261246] Write protecting the kernel read-only data: 2272k
[ 1.264224] BUG: using smp_processor_id() in preemptible [] code:
init/1
[1.265370] caller is debug_smp_processor_id+0x12/0x1
. The system finally boots... but
> > console log is polluted with:
> >
> > [9.700828] BUG: using smp_processor_id() in preemptible []
> > code: udevd/1656
> > [9.708525] caller is kfree+0x8c/0x198
> > [9.712229] CPU: 2 PID: 1656 Comm: ude
On Wed, Jan 21, 2015 at 12:38:35PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit d2dc80750ee05ceb03c9b13b0531a782116d1ade ("mm/slub: optimize
> alloc/free fastpath by removing preemption on/off
9.700828] BUG: using smp_processor_id() in preemptible [] code:
> udevd/1656
> [9.708525] caller is kfree+0x8c/0x198
> [9.712229] CPU: 2 PID: 1656 Comm: udevd Tainted: GW
> 3.19.0-rc4-00279-gd2dc80750ee0 #1630
> [9.721501] Hardware name: SAMSUNG EXYNOS
> Could you try this?
>
> powerpc/hugetlb: replace __get_cpu_var with get_cpu_var
>
> Replace __get_cpu_var safely with get_cpu_var to avoid
> the following call trace:
Confirmed, no more acktraces.
Nikita
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On 01/17/2014 05:23 PM, Nikita Yushchenko wrote:
Hi
While running LTP hugeltb tests on freescale powerpc board, I'm getting
[ 7253.637591] BUG: using smp_processor_id() in preemptible [ ]
code: hugemmap01/9048
[ 7253.637601] caller is free_hugepd_range.constprop.25+0x88/
Hi
While running LTP hugeltb tests on freescale powerpc board, I'm getting
[ 7253.637591] BUG: using smp_processor_id() in preemptible [ ]
code: hugemmap01/9048
[ 7253.637601] caller is free_hugepd_range.constprop.25+0x88/0x1a8
[ 7253.637605] CPU: 1 PID: 9048 Comm: hugem
levant WITHOUT the real-time patch
> > in the latest kernel".
> >
> >
> > > > too.
> > > >
> > > > [ 49.688847] hpsa :03:00.0: hpsa0: <0x323a> at IRQ 67 using DAC
> > > > [ 49.749928] scsi0 : hpsa
> > >
gt; >
> > > [ 49.688847] hpsa 0000:03:00.0: hpsa0: <0x323a> at IRQ 67 using DAC
> > > [ 49.749928] scsi0 : hpsa
> > > [ 49.784437] BUG: using smp_processor_id() in preemptible [
> > > ] code: kworker/u:0/6
> > > [ 49.784465]
me patch in the latest kernel
This should read, "it looks like it is relevant WITHOUT the real-time patch in
the latest kernel".
> > too.
> >
> > [ 49.688847] hpsa :03:00.0: hpsa0: <0x323a> at IRQ 67 using DAC
> > [ 49.749928] scsi0 : hpsa
> > [
.688847] hpsa :03:00.0: hpsa0: <0x323a> at IRQ 67 using DAC
> [ 49.749928] scsi0 : hpsa
> [ 49.784437] BUG: using smp_processor_id() in preemptible [
> ] code: kworker/u:0/6
> [ 49.784465] caller is enqueue_cmd_and_start_io+0x5a/0x100 [hpsa]
> [ 4
BUG: using smp_processor_id() in preemptible [
] code: kworker/u:0/6
[ 49.784465] caller is enqueue_cmd_and_start_io+0x5a/0x100 [hpsa]
[ 49.784468] Pid: 6, comm: kworker/u:0 Not tainted
3.6.11.5-rt37.52.el6rt.x86_64.debug #1
[ 49.784471] Call Trace:
[ 49.784512] [] debug_smp_process
On Wed, Mar 27, 2013 at 03:09:32PM +0100, Peter Zijlstra wrote:
> On Wed, 2013-03-27 at 10:49 +0100, Borislav Petkov wrote:
> > Ok, just for my own understanding: how do the events on the
> > ->task_ctx->event_list relate to the current cpu in this path? I mean,
> > we're on the task exit path here
On Wed, Mar 27, 2013 at 08:07:27PM +0100, Borislav Petkov wrote:
> On Wed, Mar 27, 2013 at 11:04:55AM -0700, Paul E. McKenney wrote:
> > On Wed, Mar 27, 2013 at 05:38:06PM +0100, Borislav Petkov wrote:
> > > On Wed, Mar 27, 2013 at 05:34:27PM +0100, Joerg Roedel wrote:
> > > > Interesting read, tha
On Wed, Mar 27, 2013 at 08:07:27PM +0100, Borislav Petkov wrote:
> Oh, and if one needs to brush up on RCU while doing that, there's this
> cool thing called perfbook (whole title is too long :)) I discovered
> while searching for your 3.10 queue on k.org. :-)
And here's me contributing :-):
---
On Wed, Mar 27, 2013 at 11:04:55AM -0700, Paul E. McKenney wrote:
> On Wed, Mar 27, 2013 at 05:38:06PM +0100, Borislav Petkov wrote:
> > On Wed, Mar 27, 2013 at 05:34:27PM +0100, Joerg Roedel wrote:
> > > Interesting read, thanks guys. I think I should have a look into the
> > > tree-preempt implem
1 - 100 of 132 matches
Mail list logo
