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:
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
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
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
: 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
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
On Thu, 2018-01-11 at 10:31 -0200, Ricardo Nabinger Sanchez wrote:
> Greetings,
>
> I'm getting occasional video lock-ups, and while checking logs I found
> these:
>
> ===
> [ 297.445296] BUG: using smp_processor_id() in preemptible [] code:
> claws-mail/16
Greetings,
I'm getting occasional video lock-ups, and while checking logs I found
these:
===
[ 297.445296] BUG: using smp_processor_id() in preemptible [] code:
claws-mail/1635
[ 297.445319] caller is jprobe_return+0x12/0x25
[ 297.445332] CPU: 1 PID: 1635 Comm: claws-mail Not ta
On Sun, 8 Oct 2017 20:47:10 -0700, Eric Dumazet wrote:
> This was discussed/reported earlier today by Ido.
>
> https://patchwork.ozlabs.org/patch/823011/
>
> We will submit an official fix shortly.
Ah, sorry, I missed that!
On Sun, Oct 8, 2017 at 8:43 PM, Jakub Kicinski wrote:
> Hi!
>
> This appeared in net-next over the weekend - looks likely related to
> this set...
>
> [ 164.456668] BUG: using smp_processor_id() in preemptible [] code:
> sshd/1255
> [ 164.472259] caller is ip
Hi!
This appeared in net-next over the weekend - looks likely related to
this set...
[ 164.456668] BUG: using smp_processor_id() in preemptible [] code:
sshd/1255
[ 164.472259] caller is ip6_pol_route+0xe88/0x4a80
[ 164.477571] CPU: 10 PID: 1255 Comm: sshd Not tainted
4.14.0-rc3
Ken-ichirou MATSUZAWA <[EMAIL PROTECTED]> wrote:
>
> It seems that because ipcomp_alloc_tfms() calls smp_processor_id(),
> but a comment says not need locking. Is this right?
Yes the comment is right. I'll fix it up.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV
Hello,
It seems that because ipcomp_alloc_tfms() calls smp_processor_id(),
but a comment says not need locking. Is this right?
BUG: using smp_processor_id() in preemptible [0001] code: ipcomp/2801
caller is ipcomp_init_state+0x170/0x490
Call Trace:{debug_smp_processor_id+182
21 matches
Mail list logo
